Hacker News

Thank you!! Yeah that's a good point - it's been so engrained in our brains, appreciate the feedback

yes effectively, but we use LLM vision in multiple places - for context, there are multiple ways an RPA can fail:

1. RPA code breaks (ex: throws an exception if a window does not exist) 2. RPA reports success but was clicking / typing in the wrong place 3. Underlying system breaks (virtual machine / legacy software)

the skill we have in our MCP is to build the RPA code to throw exceptions where possible so an LLM can understand the context and recover

to avoid false success states we add LLM vision steps in the workflow itself to error out if it sees that the system is in the wrong state

and for the underlying system breaking it can be as simple as having a CRON job that checks the status of the process / the health of the VM and running a script to reboot the system

it depends on the system but the pattern we've seen with RPAs is you can catch maybe 80% of the edge cases in the first week it's been rolled out

it’s a good q - we experimented a lot with computer use / agentic automation and found that at scale a hybrid solution where the automations run as deterministic code with agents for recovery is the best - running automations as code is faster & cheaper & when you’re doing critical tasks (like updating patient records) you don’t want an agent to potentially mess something up.

previously writing RPA code used to take a long time - using AI (and its infinite patience) we can write more durable code that covers more edge cases

And since they’re code based it’s pretty straightforward to an agents monitor them and update their code when upgrades to the underlying system happen etc…

for observability - we have workflow execution logs that store text, videos and screenshots so an agent or a human can debug them - lots and lots of webhooks when things break ! (:

yes good call out - that customer wheel is so overdue for an update

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

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.

Yes, more likely on a virtual machine running the legacy software

Yes! we have customers doing that

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”.

thank you - good catch (:

Thanks for flagging this!

Its an acronym for Robotic Process Automation. It usually means triggering mouse clicks and key stokes to perform tasks

It's a script that simulates clicks/keystrokes on Desktop/Web