claw-orchestrator

Run Claude Code, Codex, Antigravity, Grok Build and OpenCode behind one runtime, and a run only counts as done when checks it didn't write pass. Cross-engine fan-out, councils, session handoff, spend caps, MCP server, ACP agent.

Runssource: GitHubhomepageTypeScriptMITcommit 57ba1c95b3b7

TypeScript, MIT licensed. The project labels itself: acp, agent client protocol, agent orchestration, agentic workflow, ai agent, ai code verification, antigravity and claude code.

claw-orchestrator runs. An Argusic agent installed it in 4.5 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Project builds with npm run build, all 1724 vitest tests pass, CLI binary runs and reports version 7.5.5 with all 15 commands listed.

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.02 (measured)
recorded runs
1
last tested
stars
618
forks
104
open issues
0
watchers
4
size
20 MB
created
last push

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.

Time lost to each failure while testing claw-orchestrator, 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.

  • Node 18 pre-installed, project requires >=221.5 minutes
Install time
5 minutes
Cold machine to finish
4 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
npm test exited 0, 1724 passed across 86 test files; node dist/bin/cli.js --version returned 7.5.5
Model tokens used
43,164
Exact commit tested
57ba1c95b3b7
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.

 succeeded in 0ms:
1792243252
All good — here's the summary.
**Setup**: Node 18 was pre-installed but the project requires >=22. I installed `nvm` and `node v22…
**Verification**: `npm test` ran all 86 test files and all 1724 tests passed, zero failures. The CL…
No failures, no mocks needed, end-to-end real verification.
tokens used
43,164
All good — here's the summary.
**Setup**: Node 18 was pre-installed but the project requires >=22. I installed `nvm` and `node v22…
**Verification**: `npm test` ran all 86 test files and all 1724 tests passed, zero failures. The CL…
No failures, no mocks needed, end-to-end real verification.

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 4.5 minutes, faster than the median of the 8 comparable projects Argusic has measured.
  • Recovered from all 1 error 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 MIT, as reported by its host.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 9 acp projects Argusic has installed and timed, claw-orchestrator was the 5th fastest to reach a running state, and 7 of 9 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 4.5 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 byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.02

Topics (from GitHub)

acpagent-client-protocolagent-orchestrationagentic-workflowai-agentai-code-verificationantigravityclaude-codecodexcoding-agentdeveloper-toolsgrokmcpmodel-context-protocolmulti-agentmulti-engineopenclawopencodepersistent-sessionstypescript

Embed the badge

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

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

Questions

Does claw-orchestrator run?
Yes. claw-orchestrator runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test claw-orchestrator?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 57ba1c95b3b7. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test claw-orchestrator?
The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does claw-orchestrator take to install?
4.5 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 claw-orchestrator need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing claw-orchestrator?
1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does claw-orchestrator compare with the alternatives?
Of the 9 acp projects Argusic has installed and timed, claw-orchestrator was the 5th fastest to reach a running state, and 7 of 9 reached one at all.
Where is the evidence for claw-orchestrator?
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.

Discussion