Yes. grok-build runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 0 errors on the way, and recorded the session.

How did Argusic test grok-build?

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

What did it cost to test grok-build?

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

How long does grok-build take to install?

2 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-build need a GPU?

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

What goes wrong when installing grok-build?

Nothing did, in the recorded run: zero errors between clone and running.

Where is the evidence for grok-build?

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.

grok-build

SpaceXAI's coding agent harness and TUI. Fullscreen, mouse interactive, extensible.

Runssource: GitHubRustApache-2.0commit 37949780c144

Rust, Apache-2.0 licensed.

grok-build runs. An Argusic agent installed it in 2 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

Rust toolchain installed, project builds, debug binary runs and responds to --version and doctor, 19 crate test suites pass all 2059 tests with 0 failures.
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

verdict: Runs
Argusic Score: 60 / 100
cost of the verifying run: $0.19 (measured)
recorded runs: 2
last tested: 2026-09-15
stars: 27,035
forks: 5,098
open issues: 0
watchers: 235
size: 57 MB
created: 2026-07-14
last push: 2026-09-22

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.

Install time: 2 minutes
Cold machine to finish: 70 minutes
Errors hit and fixed: 0 hit, 0 fixed with no human help
How the result was proved: cargo build -p xai-grok-pager-bin exited 0; binary --version returned 'grok 1.0.24 (37949780c144)'; 2059 tests passed across 19 crate-level test binaries
Model tokens used: 418,905
Exact commit tested: 37949780c144
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.

| xai-grok-sandbox | 117 |
| xai-grok-shared | 136 |
| xai-grok-http | 14 |
| xai-grok-test-support | 80 |
| xai-chat-state | 362 |
| xai-compaction-transcript | 9 |
| xai-tty-utils | 73 |
| xai-file-utils | 205 |
| xai-dirs | 5 |
| xai-grok-agent | 555 |
| **Total** | **2,059 passed, 0 failed** |
No errors were encountered. Release build didn't complete within the time window (disk pressure).

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

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 2 minutes after the clone.
Following its own README: the documented path worked with nothing to fix.

Run history

tested by	attempt	outcome	score	cost USD	when
Argusic Runner	2/3	Did not run	20.00	0.27	2026-09-15 04:17 UTC
Argusic Runner	1/3	Runs	100.00	0.19	2026-09-13 08:26 UTC

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/grok-build.svg)](https://argusic.com/subject/grok-build)

Questions

Does grok-build run?: Yes. grok-build runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test grok-build?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 37949780c144. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test grok-build?: The run that produced this verdict cost $0.19: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does grok-build take to install?: 2 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-build need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing grok-build?: Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for grok-build?: 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.