agent-browser
Browser automation CLI for AI agents
Runssource: GitHubhomepageRustApache-2.0commit 5ee8691339a5
Rust, Apache-2.0 licensed.
agent-browser runs. An Argusic agent installed it in 15 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
agent-browser CLI 0.39.1: npm global install works (with Node 24+ via nvm), Chrome 155.0.8059.84 downloaded by agent-browser install, from-source Rust build compiles cleanly, all 1449 unit tests pass, all 144 Chrome-backed e2e tests pass, cargo fmt and clippy both clean.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Node.js v18.19.1 too old (requires 24+), pnpm not installed, Rust not installed, npm --prefix needed due to EACCES in /usr/local3 minutes
- e2e tests: e2e_material_checkbox_check_uncheck stack overflow under concurrent test runner1 minute
- e2e tests: 2 Obscura E2E tests fail — OBSCURA_BIN env var not set (expected, documented behavior)
- Install time
- 15 minutes
- Cold machine to finish
- 19 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- agent-browser open example.com returned 'launched browser' + 'Example Domain'; agent-browser snapshot returned full accessibility tree with refs; agent-browser close returned 'Browser closed'. Unit tests: 1449 passed, 0 failed, 148 ignored. E2E tests: 144 passed, 2 failed (Obscura requires OBSCURA_BIN).
- Model tokens used
- 141,657
- Exact commit tested
- 5ee8691339a5
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
agent-browser 0.39.1 Unknown command: help exec /bin/sh -lc 'cd /work/repo && export PATH="$HOME/.npm-global/bin:$PATH" && export NVM_DIR="$HOME/.n… exited 11 in 0ms: Your project npmrc file (/work/repo/.npmrc) has a `globalconfig` and/or a `prefix` setting, which are incompatible with nvm. Run `nvm use --delete-prefix v24.22.0` to unset it. All verification is complete. Here's the summary: tokens used 141,657 All verification is complete. Here's the summary:
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 15 minutes, faster than the median of the 13 comparable projects Argusic has measured.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 14 Rust projects Argusic has installed and timed, agent-browser was the 6th fastest to reach a running state, and 12 of 14 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Run history
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/agent-browser)Questions
- Does agent-browser run?
- Yes. agent-browser runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test agent-browser?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5ee8691339a5. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test agent-browser?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does agent-browser take to install?
- 15 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does agent-browser need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing agent-browser?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does agent-browser compare with the alternatives?
- Of the 14 Rust projects Argusic has installed and timed, agent-browser was the 6th fastest to reach a running state, and 12 of 14 reached one at all.
- Where is the evidence for agent-browser?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.