Claw Orchestrator

Claw Orchestrator Skill

Claw Orchestrator — persistent multi-engine coding session manager for claw-style agent systems. Runs as a standalone CLI/server, with first-class OpenClaw plugin support. Wraps Claude Code, Codex, Antigravity, Cursor Agent, OpenCode, and custom CLIs into headless agentic engines with 69 tools.

Engine Quick Reference

Core Workflow

javascriptCopy code
// 1. Start session (any engine)
session_start({ name: "myproject", cwd: "/path/to/project", engine: "claude" })
session_start({ name: "codex-task", cwd: "/path/to/project", engine: "codex" })
session_start({ name: "agy-task", cwd: "/path/to/project", engine: "agy" })
session_start({ name: "cursor-task", cwd: "/path/to/project", engine: "cursor" })
session_start({ name: "opencode-task", cwd: "/path/to/project", engine: "opencode", model: "anthropic/claude-sonnet-4" })

// 2. Send messages
session_send({ name: "myproject", message: "Fix the auth bug" })

// 3. Check status / search history
coding_session_status({ name: "myproject" })
session_grep({ name: "myproject", pattern: "error" })

// 4. Stop when done
session_stop({ name: "myproject" })

Session Options

CLI 2.1.111 options

CLI 2.1.121 options

stats.pluginErrors is now populated from the system/init event when CLI plugins fail to load due to unmet dependencies.

TRACEPARENT / TRACESTATE (W3C distributed tracing) are automatically forwarded from parent process env — set them before starting the session and they propagate to the child Claude CLI.

Smart defaults: When bare: true, the plugin auto-enables --exclude-dynamic-system-prompt-sections and ENABLE_PROMPT_CACHING_1H=1 unless explicitly set to false.

Multi-Agent Council

Parallel agent collaboration with git worktree isolation and consensus voting. Agents can use different engines.

javascriptCopy code
// Start a council
council_start({
  task: 'Build a REST API',
  agents: [
    { name: 'Architect', emoji: '🏗️', persona: 'System design', engine: 'claude' },
    { name: 'Engineer', emoji: '⚙️', persona: 'Implementation', engine: 'codex' },
  ],
  maxRounds: 5,
  projectDir: '/path/to/project',
});

Council lifecycle: council_start → poll council_status → council_review → council_accept or council_reject.

For details: see references/council.md

Cross-Session Messaging

Sessions can communicate. Idle sessions receive immediately; busy sessions queue.

javascriptCopy code
session_send_to({ from: "sender", to: "receiver", message: "Auth module needs rate limiting" })
session_send_to({ from: "monitor", to: "*", message: "Build failed!" })  // broadcast
session_inbox({ name: "receiver" })
session_deliver_inbox({ name: "receiver" })

Team Tools (All Engines)

All engines use the same virtual-team layer: cross-session inbox routing across active SessionManager sessions. (Claude Code's native experimental Agent Teams is in-process TUI only and not reachable from a subprocess wrapper.)

javascriptCopy code
team_list({ name: "myproject" })
team_send({ name: "myproject", teammate: "teammate", message: "Review this" })

Ultraplan & Ultrareview

• Ultraplan: Opus deep planning session (up to 30 min), produces detailed implementation plan
• Ultrareview: Fleet of 5-20 bug-hunting agents reviewing in parallel (security, logic, perf, types, etc.)

Both are async — start then poll status.

Autoloop (autonomous workspace iteration)

Autoloop uses three persistent roles. You chat with the Planner to define plan.md and goal.json; after explicit approval it starts a Coder/Reviewer iteration loop. Each role may use a different engine.

javascriptCopy code
autoloop_start({
  run_id: 'fix-parser',
  workspace: '/path/to/repo',
  planner_engine: 'claude',
  coder_engine: 'codex',
  reviewer_engine: 'agy',
});
autoloop_chat({ run_id: 'fix-parser', text: 'Read the repo and design a plan to fix the parser.' });
autoloop_chat({ run_id: 'fix-parser', text: 'Plan approved; start the loop.' });
autoloop_status({ run_id: 'fix-parser' });
autoloop_stop({ run_id: 'fix-parser', reason: 'done' });

Claude roles default to Planner opus and Coder/Reviewer sonnet. A non-Claude role with no model uses that engine's own default. Custom engine configs are supplied only at start (or HTTP resume), never by Planner output. The Reviewer runs in a restaged sandbox and returns advance/hold/rollback verdicts; push policy and SSE keep long runs observable.

For the full control protocol, registry/resume behavior, and ledger layout, see references/autoloop.md.

Tools Overview

ultracode (Claude dynamic workflows) is a session_start option, not a separate tool: set ultracode: true to have Claude orchestrate a JS workflow and fan out to subagents per task.

For full parameter reference: see references/tools.md

Run as an ACP agent

clawo acp (or the clawo-acp binary) serves Agent Client Protocol over stdio, so any ACP client — Zed, JetBrains, Neovim, Emacs, the VS Code ACP extension, or dsh through its subagent-acp provider — drives the orchestrator as its coding agent. The model selector is grouped by engine, so one dropdown spans Claude, Codex and Cursor and switching it switches engine mid-session.

For setup, the dsh YAML block, and the cancellation/permission limits: see references/acp.md

Authentication Prerequisites

Each engine requires its own auth before use:

• Claude: claude /login or ANTHROPIC_API_KEY
• Codex: codex login or OPENAI_API_KEY
• Antigravity: run agy once and complete the Google OAuth login
• Cursor: agent login or CURSOR_API_KEY
• OpenCode: opencode auth login (provider-agnostic; use provider/model form for model)