Yes. OpenCLI runs. Argusic installed and launched it on a clean machine in 26 minutes, hitting 3 errors on the way, and recorded the session.

How did Argusic test OpenCLI?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8271afc67e85. 3 attempts are recorded, and the full method is on the methodology page.

What did it cost to test OpenCLI?

The run that produced this verdict cost $0.15: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does OpenCLI take to install?

26 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 OpenCLI need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing OpenCLI?

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.

Where is the evidence for OpenCLI?

All 3 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.

OpenCLI

Make Any Website into CLI & Use your logged-in browser by AI agent.

Runssource: GitHub homepageJavaScriptApache-2.0commit 8271afc67e85

JavaScript, Apache-2.0 licensed. The project labels itself: ai agent, ai agents, ai tools, browser automation, browser use, cli and playwright.

OpenCLI runs. An Argusic agent installed it in 26 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

OpenCLI 1.8.8 builds and runs on Node 22.14.0; 632 test files pass (7325 tests, 3 skipped) across unit, extension, adapter, smoke projects; CLI binary answers version 1.8.8 and lists 1366 registered 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 100 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs
Argusic Score: 100 / 100
cost of the verifying run: $0.15 (measured)
recorded runs: 3
last tested: 2026-09-22
stars: 29,573
forks: 2,889
open issues: 287
watchers: 64
size: 16 MB
created: 2026-03-14
last push: 2026-08-30

Subject data from GitHub, linked at the top of this page, refreshed 2026-09-23. 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.

Time lost to each failure while testing OpenCLI, drawn from the recorded run — Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

@exodus/bytes ESM-only module incompatible with CJS require() in html-encoding-sniffer/jsdom caused infinite recursion under Node 20 --experimental-require-module3 minutes
Node.js v18.19.1 too old, needs >=20.18.11 minute
Missing rolldown native binding @rolldown/binding-linux-x64-gnu (npm optional dep bug)1 minute

Install time: 26 minutes
Cold machine to finish: 27 minutes
Errors hit and fixed: 3 hit, 3 fixed with no human help
How the result was proved: npm run build succeeded; node dist/src/main.js --version returned 1.8.8; vitest --project unit --project extension --project adapter --project smoke passed 7325 tests across 632 files; node dist/src/main.js list --format json registered 1366 commands; node dist/src/main.js validate passed all entries
Model tokens used: 124,992
Exact commit tested: 8271afc67e85
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.

 succeeded in 0ms:
Current time: Tue Sep 22 02:01:24 UTC 2026
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 2…
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 26, "errors": [{"msg": "No…
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 2…
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 26, "errors": [{"msg": "No…
tokens used
124,992

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 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.
Measured 3 times, so the result is not a one-off.

What did not, or is not known

Took 26 minutes to install, slower than the median of the 11 comparable projects Argusic has measured.

Of the 12 ai-agent projects Argusic has installed and timed, OpenCLI was the 11th fastest to reach a running state, and 9 of 12 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	3/3	Runs	100.00	0.15	2026-09-22 02:02 UTC
Argusic Runner	2/3	Runs	100.00	0.10	2026-09-05 04:47 UTC
Argusic Runner	1/3	Ran out of time	0.00	0.10	2026-09-05 00:45 UTC

Topics (from GitHub)

ai-agent ai-agents ai-tools browser-automation browser-use cli playwright

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/OpenCLI.svg)](https://argusic.com/subject/opencli)

Questions

Does OpenCLI run?: Yes. OpenCLI runs. Argusic installed and launched it on a clean machine in 26 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test OpenCLI?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8271afc67e85. 3 attempts are recorded, and the full method is on the methodology page.
What did it cost to test OpenCLI?: The run that produced this verdict cost $0.15: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does OpenCLI take to install?: 26 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 OpenCLI need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing OpenCLI?: 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 OpenCLI compare with the alternatives?: Of the 12 ai-agent projects Argusic has installed and timed, OpenCLI was the 11th fastest to reach a running state, and 9 of 12 reached one at all.
Where is the evidence for OpenCLI?: All 3 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.