Coasty - A Computer-Use-Agent that runs legacy software like a human
by•
Coasty is a computer use agent that operates real desktop software end to end. Started with healthcare prior auth, automating payer portals and legacy EHRs, and data removal for data privacy but now we're expanding into insurance and tax & accounting. Coasty does that work autonomously, with human takeover and full audit trails. Independently verified at 82.81% on OSWorld Verified (359 tasks), near the top of the leaderboard. No APIs required. If software has a screen, Coasty can run it.
Replies
Coasty
Driving legacy desktop software by pixels is a nightmare I know too well from automating my own stuff. How does Coasty stay reliable when a window shifts or a modal pops mid-task, does it re-read the screen each step or follow a recorded path? The surprise dialog is always where mine breaks.
Coasty
@chielephant That's why we've focused a lot on our recovery systems and making sure the agent gets back on track for pop-ups and unexpected changes. It verifies the screen after every step.
Coasty
For the developers here! Coasty is also available as an API.
You send a task in plain language, the agent gets a fresh environment, does the work, and returns structured results plus a full action log. Every click and keystroke is recorded, so you can replay exactly what the agent did. Setup takes 2 to 5 minutes per environment, then the agent runs unattended until the task is done or it decides a human should take over. It's modular so you can use the predict part of the harness to write an instruction for your own screenshots or any other part of the system. The pricing is fully transparent for every type of call you could make(at the end of Docs).
Docs are at Coasty/Docs. The quickstart gets you to a first running task in a few minutes. If you build something with it, tell me. I read everything in this thread.
@prateek_j1Â given you started with prior auth and EHRs, the "every click and keystroke recorded so you can replay exactly what the agent did" part raises a real question for that use case specifically: those replays and screenshots would routinely contain PHI on screen. where does that action log live, who can access it, and what's the retention/deletion policy on it, since the audit trail itself becomes a second copy of sensitive patient data that needs the same protection as the source system
Coasty
@prateek_j1 @galdayan So yeah, the enterprise platform is much different as you pay for compliance and HIPAA, our zero-data retention policies and security systems so none of the data is stored on our side, just acted upon.
@prateek_j1Â makes sense for the source data, but the follow-up is really about the action log itself. if every click/keystroke gets recorded so customers can replay what the agent did, that recording is capturing the same screen contents, including PHI on screen at the time. is that replay log covered by the same zero-retention policy, or does it persist somewhere (customer's own environment vs yours) since replay-ability kind of requires it to exist for at least some window
Coasty
@galdayan Great question. We treat replay artifacts differently from ordinary logs. If a session shows PHI, any screen replay, DOM snapshot, OCR text, typed values, or screenshot is considered sensitive ePHI-bearing data.
For healthcare deployments, our default posture is: no raw screen replay is persisted in Coasty-controlled infrastructure. We retain a structured audit trail of agent actions, while full replay can be disabled, redacted, short-lived, or stored only in the customer’s own environment under their retention policy.
So “zero retention” applies to raw PHI-bearing session content unless the customer explicitly enables replay under a BAA/security agreement. In that case, the retention window, storage location, access controls, and deletion policy are configured contractually, ideally customer-owned storage/VPC with strict TTL and audit access.
Coasty
If you want us to run it for you live or just in general, want to talk to us, here's our Calendly: https://cal.com/coasty/15min.
how does the per-VM teardown actually handle stateful workloads like browser automation where you need session persistence across multiple steps
Coasty
@sevgiuurelukag Our VMs last forever, irrelevant of the tasks or the number of steps. And we specialize in long-horizon tasks(30m+), so we deal with this all the time.
Is there a list of all softwares it supports?
Coasty
@ankur_jeswani It supports any software you can run on your desktop or the Virtual Machines we have, since it just uses a screen, mouse and keyboard.
Congrats on the launch!
The runs forever part is what stood out most agent VMs die when the session ends. Does it keep state between tasks, or reset each time?
Coasty
@irahimiam It keeps the state of the VM(doesn’t reset) and a snapshot when the VM fails for some reason, so you can restore and continue.
Spun up a couple of agents to test browser automation and the VM isolation actually felt real, nothing leaked between them. Pricing is noticeably cheaper than what I was paying on GCP for similar sandboxes.
Coasty
@halit1241755Â Yup, we pride ourself on providing this level of intelligence at a low rate. It should be accessible to everyone!
Spun up an agent for a browser automation test and it felt noticeably faster than my usual container setup, plus the per-VM isolation gave me real peace of mind for multi-agent runs.
Coasty
@recep728172Â What good is an isolated environment if it's not isolated haha. Glad you had a good experience!
Macaly
no-api legacy software is the perfect wedge đź‘Ź startin with healthcare prior-auth is a smart move