terminal-browser
A browser inside your terminal
Runs with mockssource: GitHubhomepageTypeScriptMITcommit 2bdf227cceb6
TypeScript, MIT licensed. The project labels itself: browser, claude code, claude code plugin, claude skills, cli, codex, herdr plugin and rust.
terminal-browser runs, with stand-ins for the services it depends on. An Argusic agent installed it in 7 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
pnpm install and pnpm -r build succeed. Node 22 with --experimental-sqlite passes all browser and shared tests (42/43 pixel tests). CLI binary runs and responds to help/version/ls commands.
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 56 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.
- import.meta.dirname unsupported on Node 18 in pixel postinstall script1 minute
- unzip binary not available in container1 minute
- node:sqlite missing on Node 18 (system Node)1 minute
- zsh shell-safety test skipped (zsh not installed in container)
- Install time
- 7 minutes
- Cold machine to finish
- 9 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- node --experimental-sqlite --test on browser/test/*.test.js (37 passed, 0 failed), shared/test/*.test.js (5 passed, 0 failed), pixel/packages/pixel/test/*.test.js (42 passed, 1 failed due to missing zsh). CLI worked: node --experimental-sqlite cli/dist/main.js --help returned usage, --version returned 'terminal-browser dev', ls returned 'no terminal browsers running'
- Model tokens used
- 87,882
- Exact commit tested
- 2bdf227cceb6
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
1. **Installed pnpm** - had to use the `curl` install script since no root and no corepack. 2. **Fixed `import.meta.dirname`** - replaced with `fileURLToPath` for Node 18/22 compatibility in … 3. **Fixed `unzip` binary missing** - replaced `unzip` call with `python3 -m zipfile -e` in pixel p… 4. **Downloaded patched Electron v44.2.0** - the postinstall script downloaded a patched electron b… 5. **Installed Node 22** - the system Node 18 doesn't have `node:sqlite`. Downloaded Node 22.11.0 f… 6. **Built all packages** - `pnpm -r build` succeeded across 16 workspace projects. **Test results:** - **browser tests**: 37/37 pass (with `--experimental-sqlite`) - **shared tests**: 5/5 pass - **pixel tests**: 42/43 pass, 6 skipped — 1 failure in `shell-safety.test.js` zsh test because `zs… - **CLI**: launches, help and version commands work, `terminal-browser ls` reports "no terminal bro… The `node:sqlite` requirement means Node 22.5+ with `--experimental-sqlite` is needed to run the ap…
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
- Installed in 7 minutes, faster than the median of the 4 comparable projects Argusic has measured.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
Of the 5 browser projects Argusic has installed and timed, terminal-browser was the 2nd fastest to reach a running state, and 4 of 5 reached one at all.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.03 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.03 |
Topics (from GitHub)
browserclaude-codeclaude-code-pluginclaude-skillsclicodexherdr-pluginrustterminalweb
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/terminal-browser)Questions
- Does terminal-browser run?
- terminal-browser runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 7 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test terminal-browser?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2bdf227cceb6. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test terminal-browser?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does terminal-browser take to install?
- 7 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 terminal-browser need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing terminal-browser?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does terminal-browser compare with the alternatives?
- Of the 5 browser projects Argusic has installed and timed, terminal-browser was the 2nd fastest to reach a running state, and 4 of 5 reached one at all.
- Where is the evidence for terminal-browser?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.