terminal
Terminal UI to get stuff done in the browser
Runssource: GitHubhomepageRustMITcommit 16cdd3ac4726
Rust, MIT licensed. The project labels itself: browser automation, browser use, cdp, terminal and tui.
terminal runs. An Argusic agent installed it in 17 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The Rust workspace builds cleanly, all 2058 Rust and 28 Python tests pass, cargo fmt is clean, and both the CLI (browser-use-terminal 0.1.8) and TUI (but 0.1.8) binaries run, with the TUI rendering its setup screen and responding to real keyboard input in a PTY session.
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 60 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.
- 22 browser-use-browser test failures: stale 15s->30s initial-wait assertion poisoned global ENV_LOCK causing cascading env-lock-poisoned panics6 minutes
- 6 browser-use-agent test failures: 5 prompt tests asserted removed phrases; 1 recovery test asserted obsolete architecture5 minutes
- cargo/rustc not installed in container2 minutes
- 1 browser-use-tui test failure: OPENROUTER_API_KEY set in container broke auth-first assertion2 minutes
- uv not installed1 minute
- tmux missing for scripts/verify-terminal-ui.sh real-terminal smoke (exit 2)1 minute
- Install time
- 17 minutes
- Cold machine to finish
- 40 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- cargo test --workspace exited 0 (2058 passed, 0 failed); python -m pytest -q exited 0 (28 passed); ./target/debug/browser-use-terminal --version printed 'browser-use-terminal 0.1.8'; TUI PTY launch rendered Setup screen and accepted Enter/Tab
- Model tokens used
- 4,006,729
- Exact commit tested
- 16cdd3ac4726
- 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.
- TUI launched in a real PTY, rendered Setup screen, answered cursor-position query, accepted Enter… - `scripts/verify-terminal-ui.sh` → all steps pass except `tmux` smoke (exits 2: `tmux is required`… tokens used 4,006,729 Both binary entry points (`but` and `browser-use-terminal`) built and answer version. Final state c… **Verification summary:** - `cargo test --workspace` → 2058 passed, 0 failed across all 11 crates - `uv run --with pytest python -m pytest -q` → 28 passed - `cargo fmt --check` → clean - `./target/debug/browser-use-terminal --version` → `browser-use-terminal 0.1.8`; `./target/debug/b… - TUI launched in a real PTY, rendered Setup screen, answered cursor-position query, accepted Enter… - `scripts/verify-terminal-ui.sh` → all steps pass except `tmux` smoke (exits 2: `tmux is required`…
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.
- Recovered from all 6 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 MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 17 minutes to install, slower than the median of the 14 comparable projects Argusic has measured.
Of the 15 browser-automation projects Argusic has installed and timed, terminal was the 15th fastest to reach a running state, and 13 of 15 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.
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 | 100.00 | 0.32 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.05 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/terminal)Questions
- Does terminal run?
- Yes. terminal runs. Argusic installed and launched it on a clean machine in 17 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test terminal?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 16cdd3ac4726. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test terminal?
- The run that produced this verdict cost $0.32: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does terminal take to install?
- 17 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 need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing terminal?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does terminal compare with the alternatives?
- Of the 15 browser-automation projects Argusic has installed and timed, terminal was the 15th fastest to reach a running state, and 13 of 15 reached one at all.
- Where is the evidence for terminal?
- 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.