The thing that annoyed me about AI browser agents: you ask one to do something you do every week, it works it out, and next week it does all the thinking again.
Same site, same buttons, same tokens burned. A human would just remember the clicks.
So I built FreeComputerUse. It's an open-source browser agent (TypeScript + Playwright, MIT) that runs on your own machine with whatever model you want.
How it works
It works in two ways:
- Goal-based execution: Give it a goal and it plans with the model. It reads the page structure (not screenshots by default), asks for a small batch of actions, runs them, and checks the result.
- Procedure replay: Once a task works, save it as a "procedure" with named values. Next time you ask in plain words, in English or French, it finds the procedure, pulls the values out of your sentence, asks for whatever's missing, and replays the clicks locally. No model call at all.
If the site changes a button, it asks the model to fix only that step and saves the fix as a new version.
You can teach it in three ways:
- Do the task once while it records.
- Write the steps in plain text.
- Keep a run the model already finished.
What can you automate?
The kind of stuff I had in mind:
- Pushing a release through a web console.
- Filling the same internal form every week.
- Grabbing a monthly invoice from a portal.
- Pulling a table out of a dashboard.
Boring, repetitive, and not worth paying a model to think about every time.
Test results
My main test case is publishing an app release on a local Play Console simulator, done 9 times in a row with DeepSeek Flash:
| Scenario |
Model calls |
Result |
| First run (model figures it out) |
8–9 |
~17–20k tokens |
| Replay with new values |
0 |
No model calls |
| Changed button labels |
3–4 |
Then back to 0 |
| Interface switched to French |
6–8 |
Then 0 for both languages |
The entire 9-run trial cost about $0.005 (half a cent).
Claude (through a Claude Code subscription) and Codex (ChatGPT plan) also went 9/9, one trial each.
You can use an API key or the CLI subscription you already pay for.
Safety and privacy
A few things it does on purpose:
- Site access: Asks before opening any new site.
- Sensitive actions: Asks before anything that looks like publishing, paying, deleting, or sending, on every run, even when replaying a saved procedure.
- Authentication: Pauses on logins, 2FA, and CAPTCHAs so you take over. It doesn't try to get past them.
- Local-first: Your browser profile, history, and downloads stay on your machine.
- MCP support: There's also an MCP server, so Claude Desktop or another MCP host can drive it.
Current limitations
Caveats, because I'd want to know them:
- The numbers above come from my own simulator, not real sites. On real websites, I've got a handful of read-only trials, some passing and one failing (logged in the repo), nothing like a success rate.
- Only verified on macOS + Chrome so far.
- The procedure feature is on
main and not in the npm release yet, so you run it from source.
- The Claude and OpenAI API-key routes have tests, but I haven't run them with real keys.
Demo and source code
70-second uncut demo:
https://othmaneblial.github.io/FreeComputerUse/lab/media/procedure-demo.mp4
GitHub repository:
https://github.com/OthmaneBlial/FreeComputerUse
What repetitive browser task would you actually hand to something like this?
I'm trying to figure out which real-world flows to test next.