Claw Orchestrator README

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.

_{One bug, one acceptance contract, five engines, three runs each, first attempt only. The runtime ran the checks itself: 9 verified, 4 refuted, 2 errored (Grok Build hit its free-tier usage limit). One task, not a benchmark. Real runs, recorded locally — how the film was made, and how to re-run it.}

Coding agents grade their own work: "All tests pass ✓". Claw Orchestrator runs them as persistent sessions behind one API and keeps the verdict out of their hands. You declare the checks, the runtime executes them and reads the exit codes, and the evidence stays on disk.

npm install -g @enderfga/claw-orchestrator
clawo serve &    # local runtime + dashboard on 127.0.0.1:18796

clawo solve "The test fails. Fix price.js." --engine codex \
  --check "npm test" --check "node ../holdout/price.spec.mjs" --wait
clawo verify <runId>    # each check, why it failed, the files that changed
clawo runs --since 1h   # every turn on every engine: model, tokens, cost, verdict

What you get

How it relates to other tools. claude-squad, Conductor and Vibe Kanban are interfaces for running agents side by side in worktrees; Claude Code subagents and Codex's parallel attempts stay within one vendor. Claw Orchestrator is a headless runtime: several vendors behind one API, durable workflows, and a verification step the agents cannot edit. They can be used together.

Quick Start

Requires Node 22+ and at least one engine CLI installed and logged in (claude, codex, agy, grok or opencode).

npm install -g @enderfga/claw-orchestrator
clawo serve   # dashboard at http://127.0.0.1:18796/dash

The server writes an access token to ~/.openclaw/server-token; the CLI reads it from there. Open http://127.0.0.1:18796/login?token=<token>&redirect=/dash once to sign in the browser.

From a terminal:

clawo solve "Fix the failing tests" --engine claude --check "npm test" --wait
clawo fanout "How would you speed up this test suite?" --engines claude,codex,grok --synthesize --wait
clawo workflow list

From Claude Code, or any MCP host:

claude mcp add clawo -- clawo-mcp

Then ask for workflow_start with template solve, a task, and a contract such as {"checks":[{"type":"command","cmd":"npm","args":["test"]}]}.

From TypeScript:

import { SessionManager } from '@enderfga/claw-orchestrator';

const manager = new SessionManager();
await manager.startSession({ name: 'fix-tests', engine: 'claude', cwd: '/project' });
const result = await manager.sendMessage('fix-tests', 'Fix the failing tests');

All features

The full 78-tool surface is enumerated in tools.md.

Integrations

Standalone CLI

clawo serve                                            # dashboard + HTTP server on :18796
clawo session-start fix-tests --engine claude --cwd .  # start a session
clawo session-send fix-tests "Fix the failing tests"   # send into it

Every command is documented in cli.md.

OpenClaw Plugin

curl -fsSL https://raw.githubusercontent.com/Enderfga/claw-orchestrator/main/install.sh | bash

Installs via npm, registers the plugin in ~/.openclaw/openclaw.json, restarts the gateway. All 78 tools become available to every OpenClaw agent.

Model Context Protocol Server

npm install -g @enderfga/claw-orchestrator   # clawo-mcp is now on PATH

Register clawo-mcp with any MCP-compatible host: Hermes Agent, Claude Desktop, Cursor, Cline, Continue, Zed, Windsurf, Goose, and others. Per-host stdio-config snippets and the CLAWO_MCP_TOOLS allowlist for tight tool budgets are in mcp.md.

Agent Client Protocol Agent

clawo acp        # or the dedicated binary: clawo-acp

MCP gives tools to an agent; ACP makes you be the agent. clawo acp speaks Agent Client Protocol over stdio, so Zed, JetBrains, Neovim, Emacs, the VS Code ACP extension — or dsh via its subagent-acp provider — can drive Claw Orchestrator as their coding agent.

The model selector is grouped by engine, so one dropdown holds Claude, Codex and Grok models at once and switching it switches engine mid-session; /council, /ultraplan and /ultrareview run multi-agent orchestrations from the chat box. Setup, the dsh YAML block, and the cancellation and permission limitations are in acp.md.

Engine Compatibility

Any coding CLI that runs as a subprocess can be wired up as a custom engine — see multi-engine.md.

How the engine table stays current

The versions above are not typed in — they are what the weekly sweep last ran. scripts/sweep.ts measures each core engine's installed, pinned and upstream version, diffs the flags the wrapper passes against the binary's --help, runs one live turn through the real wrapper class, smokes the ACP and MCP entry points, and checks src/models.ts against both vendors' published price tables. It contains no model call, so the check that reports a wrapper as broken does not share the wrapper's failure modes.

scripts/sweep-workflow.json wraps the same script as a durable run on this project's own kernel: verifier → router → an agent that drafts the alignment on a sweep/<date> branch → a human gate. A person reviews and merges; the orchestrator does not edit its own code unattended.

Contributing

See CONTRIBUTING.md. Run npm run build && npm run lint && npm run format:check && npm run test before submitting.

License

MIT — see LICENSE.