Yes. zx runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 4 errors on the way, and recorded the session.

How did Argusic test zx?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 65fc542d88ba. One attempt is recorded, and the full method is on the methodology page.

What did it cost to test zx?

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 zx take to install?

8 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.

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

What goes wrong when installing zx?

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.

Where is the evidence for zx?

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.

zx

A tool for writing better scripts

Runssource: GitHub homepageJavaScriptApache-2.0commit 65fc542d88ba

JavaScript, Apache-2.0 licensed. The project labels itself: bash, child process, cli, exec, javascript, nodejs, pipe and shell.

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

npm install succeeds, npm run build completes cleanly, CLI responds to --version (8.9.0), --help, -e, and script-run modes, all unit tests pass (error 10/10, log 11/11, md 6/6, util 12/12, vendor 8/8, global 2/2, export 3/3, index 2/2, deps 10/10, goods 29/29, core 133/133 pass)
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.19 (measured)
recorded runs: 1
last tested: 2026-10-08
stars: 45,782
forks: 1,308
open issues: 13
watchers: 173
size: 4 MB
created: 2021-05-05
last push: 2026-10-06

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

CLI silently produced no output: isMain() always returned false on Node.js because import.meta.main is undefined (Deno-only)8 minutes
core test failed: Promise.withResolvers is not a function (Node 22+ API, container runs Node 18)3 minutes
log.test.ts failures when NO_COLOR=1 env is set (chalk colors suppressed, tests expect ANSI)
cli.test.js hangs after test 16 due to stale TCP connection in fakeServer (test 17 fake server's 500 response leaves dangling conn)

Install time: 8 minutes
Cold machine to finish: 24 minutes
Errors hit and fixed: 4 hit, 4 fixed with no human help
How the result was proved: node build/cli.js --version returned "8.9.0", --help prints usage, -e "console.log(\"verified\")" printed "verified", running a .mjs script executed correctly
Model tokens used: 144,674
Exact commit tested: 65fc542d88ba
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.

    ],
    'test_depth': 'tier1_real',
    'notes': 'Installed zx 8.9.0 from source. Fixed isMain() autorun for Node.js (no import.meta.ma…
    'verified_how': 'node build/cli.js --version returned \\\"8.9.0\\\", --help prints usage, -e \\…
    'final_state': 'npm install succeeds, npm run build completes cleanly, CLI responds to --versio…
}
print('ARGUSIC_RESULT: ' + json.dumps(result))
\"" in /work/repo
 succeeded in 0ms:
2026-10-08T07:40:07.113118Z ERROR codex_core::session: failed to record rollout items: thread 01a11…
tokens used
144,674

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 4 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.

What did not, or is not known

Took 8 minutes to install, slower than the median of the 9 comparable projects Argusic has measured.
Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 10 bash projects Argusic has installed and timed, zx was the 6th fastest to reach a running state, and 7 of 10 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 8 minutes after the clone.

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	1/3	Runs	100.00	0.19	2026-10-08 07:40 UTC

Topics (from GitHub)

bash child-process cli exec javascript nodejs pipe shell spawn

Embed the badge

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

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

Questions

Does zx run?: Yes. zx runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test zx?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 65fc542d88ba. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test zx?: 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 zx take to install?: 8 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 zx need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing zx?: 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 zx compare with the alternatives?: Of the 10 bash projects Argusic has installed and timed, zx was the 6th fastest to reach a running state, and 7 of 10 reached one at all.
Where is the evidence for zx?: 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.

zx