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.
Not yet testedsource: 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 has not been verified yet.
Measured by Argusic on a fresh machine every time. Every number links to its evidence.
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.
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
No recorded runs.
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.
[](https://argusic.com/subject/claw-orchestrator)Questions
- Does claw-orchestrator run?
- claw-orchestrator has not been fully verified yet. No recorded run has produced a verdict yet.
- How did Argusic test claw-orchestrator?
- On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.
- Where is the evidence for claw-orchestrator?
- All 0 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.