// Spawn and manage sibling Claude Code agents through claude-agent for parallel frontend, workbench, implementation, and review tasks.
| name | claude-code-orchestrator |
| description | Spawn and manage sibling Claude Code agents through claude-agent for parallel frontend, workbench, implementation, and review tasks. |
Use the local claude-agent CLI to run background Claude Code agents in tmux:
claude-agent start "Task prompt" --dir /path/to/repo --map --xhigh
claude-agent await-turn <jobId>
claude-agent capture <jobId> 160 --clean
claude-agent send <jobId> "Continue with this correction."
Defaults are --model opus --effort max --permission-mode auto. Use --xhigh for broad workbench variant generation and default max for final review or hard implementation passes.
For workbench jobs, keep the prompt compact:
Read apps/workbench/AGENT_DESIGN_RULES.md, src/generated/theme-summary.md, and the target brief.md.
Create v1-v5 distinct variants, run bun run check, and report files changed.
Use claude-agent jobs --json for compact status. Use claude-agent attach <jobId> for direct tmux interaction.
Runs Opus/Claude Code agents through the local claude-agent tmux CLI/service for codebase exploration, frontend/workbench variants, implementation support, and second-model review. Trigger on /opus-agent-orchestrator, opus-agent, claude-agent, use opus agents, spawn opus, Claude Code agents, frontend variants, workbench variants, explore with Opus. Pairs with codex-orchestrator: Codex remains commander; Opus agents are specialist scouts/builders.
Use when Codex should spawn, monitor, steer, or review Claude Code agents through the local claude-agent tmux CLI/service, especially for frontend workbench variants and Opus design passes.