A computer-use agent for operations work
Screen work, done and proven.
Guli runs a computer-use agent that types into software with no API. It carries one task from app to app, holds anything that looks wrong for a person, and reads back every entry it writes.
Where scripts stop
Reading the page is the easy part.
Scrapers and API scripts are good at pulling data out. Operations work is putting it somewhere, across apps, without making a mess.
| Topic | A script, scraper or RPA bot | The computer-use agent we run | See it |
|---|---|---|---|
| When the screen surprises it | Runs the steps it was written for. A pop-up it did not expect can stop it. | Closes a pop-up it was not told about and carries on. Spots a likely duplicate, saves the bill on hold and writes why for a person. | |
| One app or many | One site or one system per script. | One task across a supplier portal, a PDF and an accounting app. | |
| Reads or writes | Writes only through an API, or a selector someone coded for each field. | Types the invoice into an accounting app with no API. | |
| Proof | Checks only what its author thought to assert. | Ends on the saved bill and reports its status. Every saved value is then checked against the PDF from the run log. |
This describes the common case, not every tool. The agent is slower than a script. It's for the steps a script can't do. We seeded the pop-up and the duplicate; the agent handled them on its own. The portal and accounting app are mock apps we built without an API; their source is linked with the uncut run.
Scenario
One invoice, from a supplier portal to an accounting app with no API.
A supplier portal, a PDF and an accounting app that were never built to talk to each other. The agent works through all three on screen, holds what looks like a duplicate, and reads back what it wrote.
- Works in
- A supplier portal, the invoice PDF, your accounting app
- Writes into
- The accounting form: invoice number, date and amount
- Stops and asks when
- An entry looks like one that already exists. It asks a person by email.
- Proves it
- Reads every value back from the screen and saves a screenshot
Offered · not shown in a film yet
- Benefits and HR portals: changes from your spreadsheet entered portal by portal, held when the portal disagrees with the sheet.
- Renewals and filings: state forms filled from your records, stopped before submit for a person to sign off.
- Orders from email: purchase orders keyed into an order screen with no import, held when a code or price does not match.
How a run ends
Nothing counts as done until it is read back.
Work the screen
It signs in with the accounts you give it, reads the screen and types into the fields.
Stop on doubt
A pop-up it was not told about, or an entry that looks already made. It handles what it can and holds the rest for a person.
Read back
It reads each value back from the screen it wrote to and saves a screenshot. Then the record is marked done.
Security
You name what it can touch.
- Access
- You choose which accounts and sites the agent may use, for each workflow.
- Doubt
- When a record looks wrong or doubled, the agent holds it and asks a person by email instead of posting it.
- Evidence
- Every write is read back and saved with a screenshot. Screenshots are available on request.
Have specific security or access requirements? Put them in your request and we will answer each one directly.
100+ clients servedBacked by angel investors
Send us the work no API can reach.
Name the apps, the steps and how often. We reply by email.
Every record is read back after it is written.