grok-cli
An open-source coding agent for the Grok API
Runs with mockssource: GitHubTypeScriptMITcommit fb97af83f06d
TypeScript, MIT licensed. The project labels itself: agents, ai, cli, code, coding agent, grok and xai.
grok-cli runs, with stand-ins for the services it depends on. An Argusic agent installed it in 14 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
All 248 tests pass (48 files), project builds cleanly with tsc, CLI responds to --help, --version, and models commands via Bun runtime.
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 92 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.
- bun:sqlite built-in not available when vitest runs under Node7 minutes
- Node.js 18 too old — vitest 4.x requires styleText from node:util (Node 20+)4 minutes
- Bun not installed (unzip missing for install.sh, npm global install fails without --prefix)2 minutes
- Built CLI fails with ERR_MODULE_NOT_FOUND under node (uses Bun-native module resolution)1 minute
- Install time
- 14 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- bun run test: 48 test files passed, 248 tests passed. bun run dist/index.js --version returned 1.1.7. bun run dist/index.js --help and models command printed correctly.
- Model tokens used
- 232,639
- Exact commit tested
- fb97af83f06d
- 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
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 2, run , the attempt that decided the verdict above. 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.
test tools types ui utils verify wallet cleaned All tests pass (48 files, 248 tests), the project builds cleanly with `tsc`, and the CLI responds t… tokens used 232,639 All tests pass (48 files, 248 tests), the project builds cleanly with `tsc`, and the CLI responds t…
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
- 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.
- Took 14 minutes to install, slower than the median of the 7 comparable projects Argusic has measured.
Of the 8 agents projects Argusic has installed and timed, grok-cli was the 8th fastest to reach a running state, and 5 of 8 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.07 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.04 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/grok-cli)Questions
- Does grok-cli run?
- grok-cli runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 14 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test grok-cli?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit fb97af83f06d. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test grok-cli?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does grok-cli take to install?
- 14 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 grok-cli need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing grok-cli?
- 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 grok-cli compare with the alternatives?
- Of the 8 agents projects Argusic has installed and timed, grok-cli was the 8th fastest to reach a running state, and 5 of 8 reached one at all.
- Where is the evidence for grok-cli?
- 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.