Does CodeMachine-CLI run?

Argusic could not verify that CodeMachine-CLI runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 0 errors on the way, and recorded the session.

How did Argusic test CodeMachine-CLI?

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

What did it cost to test CodeMachine-CLI?

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

How long does CodeMachine-CLI take to install?

3 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 CodeMachine-CLI need a GPU?

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

What goes wrong when installing CodeMachine-CLI?

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

Where is the evidence for CodeMachine-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.

CodeMachine-CLI

CodeMachine is an open-source tool that orchestrates AI coding agents into repeatable, long-running workflows. ⚡️

Could not verifysource: GitHub homepageTypeScriptApache-2.0commit 572def63eb80

TypeScript, Apache-2.0 licensed. The project labels itself: ai, automation, cli, cli tool, code generation, developer tools, generative ai and multi agent systems.

Argusic could not get CodeMachine-CLI running. An Argusic agent installed it in 3 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

CodeMachine CLI v0.8.0 installs via 'bun install' (591 packages), responds to all CLI subcommands (help, version, auth, run, step, templates, agents, mcp, import, export), and launches its TUI interface. No test suite exists in the repository.
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 75 of 100 (the mean of this project's run scores).

At a glance

verdict: Could not verify
Argusic Score: 75 / 100
cost of the verifying run: $0.03 (measured)
recorded runs: 2
last tested: 2026-10-03
stars: 2,512
forks: 236
open issues: 10
watchers: 36
size: 32 MB
created: 2025-09-28
last push: 2026-02-25

Subject data from GitHub, linked at the top of this page, refreshed 2026-10-03. 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: 3 minutes
Cold machine to finish: 5 minutes
Errors hit and fixed: 0 hit, 0 fixed with no human help
How the result was proved: bun --conditions=browser src/runtime/cli-setup.ts --version returned '0.8.0' (exit 0); bun --conditions=browser src/runtime/cli-setup.ts --help returned usage (exit 0); bun --conditions=browser src/runtime/cli-setup.ts templates list returned 'CodeMachine Workflow Builder' (exit 0); bun --conditions=browser src/runtime/cli-setup.ts agents list returned agent listing (exit 0); TUI launched and produced terminal output when run without flags
Model tokens used: 114,674
Exact commit tested: 572def63eb80
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
Whether it works at all: this run verified nothing, so this page makes no claim either way

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

exec
/bin/sh -lc 'export PATH="$HOME/bin:$PATH" && cd /work/repo && bun --conditions=browser src/runtime…
 succeeded in 226ms:
────────────────────────────────────────────────────────────
Total: 0 agents (0 active, 0 offline)
EXIT: 0
Now let me produce the final result.
2026-10-03T13:25:28.163014Z ERROR codex_core::session: failed to record rollout items: thread 01a10…
2026-10-03T13:25:28.163955Z ERROR codex_core::session: failed to record rollout items: thread 01a10…
tokens used
114,674
Now let me produce the final result.

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

Installed in 3 minutes, faster than the median of the 78 comparable projects Argusic has measured.
Nothing broke on the way: zero errors between clone and running.
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

An agent with no time limit did not get it running.

Of the 79 ai projects Argusic has installed and timed, CodeMachine-CLI was the 24th fastest to reach a running state, and 56 of 79 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	Unverified	80.00	0.03	2026-10-03 13:25 UTC
Argusic Runner	1/3	Unverified	70.00	0.04	2026-10-03 13:20 UTC

Topics (from GitHub)

ai automation cli cli-tool code-generation developer-tools generative-ai multi-agent-systems orchestration scaffolding workflow-automation

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/CodeMachine-CLI.svg)](https://argusic.com/subject/codemachine-cli)

Questions

Does CodeMachine-CLI run?: Argusic could not verify that CodeMachine-CLI runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test CodeMachine-CLI?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 572def63eb80. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test CodeMachine-CLI?: The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does CodeMachine-CLI take to install?: 3 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 CodeMachine-CLI need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing CodeMachine-CLI?: Nothing did, in the recorded run: zero errors between clone and running.
How does CodeMachine-CLI compare with the alternatives?: Of the 79 ai projects Argusic has installed and timed, CodeMachine-CLI was the 24th fastest to reach a running state, and 56 of 79 reached one at all.
Where is the evidence for CodeMachine-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.