HN.zip

Launch HN: Minicor (YC P26) – Windows desktop automations at scale

Hey we’re Faiz and Saheed and we built Minicor so AI companies who need to integrate to desktop systems with no API can quickly build scalable desktop RPAs. Demo: https://www.youtube.com/watch?v=MD0GHZIJ1cwWe were working on non-RPA integrations when a customer promised to sign a deal in 2 days if we could unblock a sale of theirs that involved integrating with a clinic’s Windows based medical record system. We didn’t know it at the time but it turns out that building desktop RPAs at scale is extremely difficult because scripting is hard (learning the system, defining the automation, UIs changing constantly), orchestration is hard (is the VM up? queuing, parallelizing) and debugging is hard (zero observability, false positives, cascading failures). 30%+ failure rates are not uncommon. At scale we’ve seen cases of failed RPAs leading to thousands of support tickets a month.To solve the problems we were facing, we built an MCP that Claude Code/Codex can use to navigate a virtual machine running desktop software with Python to create RPA workflows. The RPA workflows run as Python scripts for speed, cost, and determinism. These workflows can be triggered by API following any input/output schema specified, with video replays and logs stored with each run. The MCP can debug RPAs and make changes to the underlying code, all of which are version controlled. We also built tools for cloning VMs for parallelizing RPAs, and handling 2FA/OTP challenges. Plus since workflows are code based: we were also able to add triggers for Slack notifications, human-in-the-loop steps, or call an LLM to verify the state of a VM by passing a screenshot.Would love to hear your feedback and if you have any RPA horror stories! (:

41 points by fchishtie - 23 comments

23 Comments

polonbike [3 hidden]5 mins ago
Congrats on the launch. One complaint: RPA this, non-RPA that, but you never explain what it means. I would write down the acronym fully once at the first mention on the landing page.
fchishtie [3 hidden]5 mins ago
Thank you!! Yeah that's a good point - it's been so engrained in our brains, appreciate the feedback
a-dub [3 hidden]5 mins ago
i'm curious: how does the steady state error rate of a stochastic automated system like this compare with the downtime and errors that come from a (brittle) deterministic bridge that can fail with upgrades? what does the observability look like? (i'm guessing one feature is that the execution log including images/screenshots for each transaction gets saved, which is probably a huge improvement.)
dragonsenseiguy [3 hidden]5 mins ago
Small website nitpick: I feel like the "In production with" section's companies logos should be a bit darker, I could barely tell there was something there.
fchishtie [3 hidden]5 mins ago
yes good call out - that customer wheel is so overdue for an update
theaniketmaurya [3 hidden]5 mins ago
Congrats on the launch! Legacy system users are also one of the slowest to adopt AI. How do you navigate that?
fchishtie [3 hidden]5 mins ago
100% right - we support the AI companies who are selling to the legacy end users - for ex: we don’t sell directly to hospitals, but an AI scribe for doctors that already has a hospital as a customer, we help them integrate to the hospital’s EMR
debarshri [3 hidden]5 mins ago
Legacy system users are also the one who pays the most for tools and services. We sell to enterprise, I can attest to that. If it is relevant usecase and positioning for the market, it should be fine.
fchishtie [3 hidden]5 mins ago
yeah it’s been interesting to watch, we were surprised initially at how much legacy users actually wanted to adopt AI - I think it’s because of how awful the old software can be to interact with
snozolli [3 hidden]5 mins ago
Computer use agents that run on Windows VMs or in the browser. On-premise, cloud

I think you meant premises.

https://brians.wsu.edu/2016/05/30/premise-premises/

throw03172019 [3 hidden]5 mins ago
I’ve never heard a customer say “on-premises” when talking about servers they run. On-premise is usually the term regardless if it is “correct”.
fchishtie [3 hidden]5 mins ago
thank you - good catch (:
throw03172019 [3 hidden]5 mins ago
So AI companies would install this on their customer (practices) computers?
fchishtie [3 hidden]5 mins ago
Yes, more likely on a virtual machine running the legacy software
throw03172019 [3 hidden]5 mins ago
Thanks. Most practices are not tech savvy. So how would the VM setup work in their own network / machines?
fchishtie [3 hidden]5 mins ago
Yeah that’s true - in those cases we’ve either worked with their outsourced IT provider to spin up VMs for us or have had to spin up our own VM and connect through a VPN - IT can be very fun…
mingabunga [3 hidden]5 mins ago
Could you use this to test new releases of software for bugs? A bit like TDD but for GUI interactions
fchishtie [3 hidden]5 mins ago
Yes! we have customers doing that
throw03172019 [3 hidden]5 mins ago
Please make your trust center public if you are focusing on healthcare AI companies…the footer link is dead.
fchishtie [3 hidden]5 mins ago
Thanks for flagging this!
Boxxed [3 hidden]5 mins ago
What the deuce is an "RPA"?
saheed_laminar [3 hidden]5 mins ago
Its an acronym for Robotic Process Automation. It usually means triggering mouse clicks and key stokes to perform tasks
fchishtie [3 hidden]5 mins ago
It's a script that simulates clicks/keystrokes on Desktop/Web