Uni-CLI
One command for every interface, search, run, and inspect real software across APIs, browsers, desktops, local tools, and MCP.
Runssource: GitHubhomepageTypeScriptApache-2.0commit aed1a389b748
TypeScript, Apache-2.0 licensed. The project labels itself: agent infrastructure, ai agents, ai tools, automation, browser automation, cdp, chrome and claude code.
Uni-CLI runs. An Argusic agent installed it in 42 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Uni-CLI v1.2.1 builds from source, runs 3735 passing unit tests, and executes live commands (hackernews top, search, doctor) against real remote APIs on Node 22.23.4 (npm v10.9.9). The npm global package v1.3.0 is also installed and functional.
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.
- System node v18.19.1 is below the project minimum v22.19 — npm install, build, and tests all fail without a compatible Node4 minutes
- Install time
- 42 minutes
- Cold machine to finish
- 20 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- npm test exited 0: 331 test files passed, 3735 tests passed, 6 skipped; unicli hackernews top --limit 1 -f json returned a real Hacker News story (ok: True, count: 1) with no auth required; unicli search 'hacker news' -f json returned 8 results; unicli doctor shows all 338 sites loaded, broker/Normal, ffmpeg installed
- Model tokens used
- 46,256
- Exact commit tested
- aed1a389b748
- 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.
import sys, json
d = json.load(sys.stdin)
print('"'search ok:', d['ok'], '| results:', d['meta']['count'])
\"" in /work/repo
succeeded in 1223ms:
Now using node v22.23.4 (npm v10.9.9)
1.3.0
search ok: True | results: 8
All verified end-to-end. Here's the result:
tokens used
46,256
All verified end-to-end. Here's the result: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 1 error 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
- Took 42 minutes to install, slower than the median of the 6 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 7 agent-infrastructure projects Argusic has installed and timed, Uni-CLI was the 7th fastest to reach a running state, and 7 of 7 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
Topics (from GitHub)
agent-infrastructureai-agentsai-toolsautomationbrowser-automationcdpchromeclaude-codeclicodexcursordeveloper-toolsmcpmcp-servernodejsopenaiself-repairtypescriptweb-scrapingyaml
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/uni-cli)Questions
- Does Uni-CLI run?
- Yes. Uni-CLI runs. Argusic installed and launched it on a clean machine in 42 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test Uni-CLI?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit aed1a389b748. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test Uni-CLI?
- The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Uni-CLI take to install?
- 42 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 Uni-CLI need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Uni-CLI?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does Uni-CLI compare with the alternatives?
- Of the 7 agent-infrastructure projects Argusic has installed and timed, Uni-CLI was the 7th fastest to reach a running state, and 7 of 7 reached one at all.
- Where is the evidence for Uni-CLI?
- 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.