Nördnytt! 🤓Launch HN: Minicor (YC P26) – Windows desktop automations at scale
We 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! (:
- polonbike - 9815 sekunder sedanCongrats 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.
- throw03172019 - 1081 sekunder sedanBiggest question is how much of this can be stored / processed on our own infra and with our own lifecycle rules? For example, this can touch a lot of PHI. Screenshots, videos, JSON inputs/outputs etc.
- throw03172019 - 3079 sekunder sedanDoes this only revert back to LLM Vision when it catches an error? I.e once the RPA / workflow is built once, it’s efficient for running multiple times (until it catches an error state)?
- dragonsenseiguy - 6573 sekunder sedanSmall 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.
- ilundin - 1701 sekunder sedanIs the cloud LLM the judge based on screenshots with patient/customer data included ? That seems like a no-go for many countries given privacy concerns ?
- a-dub - 3967 sekunder sedani'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.)
- throw03172019 - 1872 sekunder sedanHow does this compare with CyberDesk (also YC)?
- theaniketmaurya - 7742 sekunder sedanCongrats on the launch! Legacy system users are also one of the slowest to adopt AI. How do you navigate that?
- throw03172019 - 7098 sekunder sedanSo AI companies would install this on their customer (practices) computers?
- mingabunga - 11668 sekunder sedanCould you use this to test new releases of software for bugs? A bit like TDD but for GUI interactions
- snozolli - 4048 sekunder sedanComputer use agents that run on Windows VMs or in the browser. On-premise, cloud
I think you meant premises.
- throw03172019 - 7500 sekunder sedanPlease make your trust center public if you are focusing on healthcare AI companies…the footer link is dead.
- Boxxed - 11657 sekunder sedanWhat the deuce is an "RPA"?
- viveksingh_17 - 6247 sekunder sedan[flagged]