CLI-Anything
"CLI-Anything: Making ALL Software Agent-Native" -- CLI-Hub: https://clianything.cc/
Runssource: GitHubhomepagePythonApache-2.0commit 810c18b0d1ab
Python, Apache-2.0 licensed.
CLI-Anything runs. An Argusic agent installed it in 0.1 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
cli-anything-hub 0.4.1 is installed in a venv at /work/repo/venv, all 164 tests pass, and the cli-hub CLI commands (list, search, info, --version) return correct output from the live remote registry.
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 94.7 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.
- Install time
- under a minute
- Cold machine to finish
- 2 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- cli-hub --version returned 'cli-hub 0.4.1'; cli-hub list returned 103 CLIs from the live remote registry; cli-hub search gimp returned valid entry; pytest tests/ exited 0 with 164 passed
- Model tokens used
- 36,281
- Exact commit tested
- 810c18b0d1ab
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
/bin/sh -lc '/work/repo/venv/bin/cli-hub --version 2>&1' in /work/repo succeeded in 381ms: All done. Here's what I observed: **Install**: Created a venv, installed `cli-anything-hub` via `pip install -e .` — no errors. **Tests**: 164/164 passed in 2.64s using the bundled test suite. **Verification**: Ran the actual CLI commands against the real remote registry — `cli-hub --help`, … tokens used 36,281 All done. Here's what I observed: **Install**: Created a venv, installed `cli-anything-hub` via `pip install -e .` — no errors. **Tests**: 164/164 passed in 2.64s using the bundled test suite. **Verification**: Ran the actual CLI commands against the real remote registry — `cli-hub --help`, …
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 0.1 minutes, faster than the median of the 3 comparable projects Argusic has measured.
- Nothing broke on the way: zero errors between clone and running.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
- Measured 4 times, so the result is not a one-off.
Of the 4 Python projects Argusic has installed and timed, CLI-Anything was the 1st fastest to reach a running state, and 3 of 4 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.
- A quick evaluation: it was running 0.1 minutes after the clone.
- Following its own README: the documented path worked with nothing to fix.
Run history
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/cli-anything)Questions
- Does CLI-Anything run?
- Yes. CLI-Anything runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test CLI-Anything?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 810c18b0d1ab. 4 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test CLI-Anything?
- The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does CLI-Anything take to install?
- 0.1 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 CLI-Anything need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing CLI-Anything?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does CLI-Anything compare with the alternatives?
- Of the 4 Python projects Argusic has installed and timed, CLI-Anything was the 1st fastest to reach a running state, and 3 of 4 reached one at all.
- Where is the evidence for CLI-Anything?
- All 4 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.