zx
A tool for writing better scripts
Runssource: GitHubhomepageJavaScriptApache-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 66 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
zx installs and builds cleanly on Node 18.19.1, the CLI answers --version with 8.9.0 and executes shell-template scripts end to end, the unit suite passes 265/0/2 via tsx, and the packed npm artifact installs and runs.
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
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.
- CLI silently no-op on Node 18/20: isMain relied on import.meta.main (Node 24+) so autorun() never ran12 minutes
- test/core.test.js used Node 22-only assert.unreachable() and Promise.withResolvers()8 minutes
- chalk color mismatch: container NO_COLOR=1 disabled ANSI so log.test.ts failed; FORCE_COLOR changed chalk.level breaking generated export.test.js8 minutes
- npm test unit step needs Node 24 flag --experimental-transform-types, absent on Node 18.19.16 minutes
- test:size exceeded limits by ~130 B due to isMain fix5 minutes
- test/cli.test.js non-std-ext assertion hard-coded checkout path basename 'zx'4 minutes
- Install time
- 66 minutes
- Cold machine to finish
- 67 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- How the result was proved
- env -u NO_COLOR FORCE_COLOR=3 npx tsx ./test/all.test.js exited 0 with 265 pass, 0 fail, 2 skipped; node build/cli.js --version printed 8.9.0; fresh-dir npm install /work/repo then ./node_modules/.bin/zx ran a script executing $`echo new-user-zx-works` (captured) and $`expr 20 + 22` (stdout '42'); npm run test:npm exited 0 with 6 pass; test:types, test:license, cjs/mjs/tsx/ts-node/tsc smokes, test:circular, test:jsr, test:size, fmt:check all passed
- Model tokens used
- 314,596
- 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/core.test.js`: used Node 22-only APIs (`assert.unreachable`, `Promise.withResolvers`). Repl… - `npm test`'s unit step needs Node 24's `--experimental-transform-types` (not available on Node 18… - Chalk color detection: the container exports `NO_COLOR=1`, so `log.test.ts` (expects ANSI colors)… - `test/cli.test.js`: one assertion hard-coded the checkout path basename `zx/...`; made it path-in… - `.size-limit.json`: the `isMain` fix added ~130 B to the bundle, tripping the size limits; bumped… - `test/it/build-npm.test.js`: `node -e 'import ...'` fails on Node 18 without `--input-type=module… **Verified** - `npm install` succeeded (522 packages) and `npm run build` succeeded. - Full unit suite: `env -u NO_COLOR FORCE_COLOR=3 npx tsx ./test/all.test.js` → `# tests 267, # pas… - `npm run test:types` (tsd), `test:license`, `test:smoke:cjs`, `test:smoke:mjs`, `test:smoke:tsx`,… - New-user flow: in a fresh dir, `npm install /work/repo` → `./node_modules/.bin/zx --version` → `8… - `test:audit` exits 1 due to pre-existing dev-dependency advisories (vitepress→vite) in the upstre…
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 7 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 2 times, so the result is not a one-off.
What did not, or is not known
- Took 66 minutes to install, slower than the median of the 11 comparable projects Argusic has measured.
Of the 12 bash projects Argusic has installed and timed, zx was the 12th 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
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/zx)Questions
- Does zx run?
- Yes. zx runs. Argusic installed and launched it on a clean machine in 66 minutes, hitting 7 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. 2 attempts are 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.36: 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?
- 66 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?
- 7 things broke in the recorded run, and 7 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 12 bash projects Argusic has installed and timed, zx was the 12th fastest to reach a running state, and 9 of 12 reached one at all.
- Where is the evidence for zx?
- 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.