| name | orchestrator |
| description | Coordinate complex work across workers while keeping product context and final judgment in the main session. Use when the user asks to orchestrate, delegate, parallelize, supervise workers, or coordinate multi-agent implementation, research, review, or verification from Codex App, Claude Code, or Cursor. |
Orchestrator
Read ~/dev/agent-guards/AGENTS.md.
The main session owns product context, task decomposition, supervision, integration, verification, and final reporting. Workers own bounded research, implementation, cleanup, or review. Do not turn the orchestrator into another implementation worker.
Select The Host Path
Keep host mechanisms separate:
- Codex: use native subagents for bounded work. When the user approves and work needs durable context isolation, an independent lifecycle, or follow-up across turns, use a separate Codex task managed through the pinned project orchestrator. The orchestrator remains the user's interface: send messages, surface questions and meaningful progress, integrate results, and archive completed tasks.
- Claude Code: use native subagents, with headless Pi workers as the fallback when native subagents are unavailable or unsuitable.
- Cursor: use Cursor's native worker/subagent capabilities from the IDE or agent window, with Grok 4.5 High as the default worker model. Trust Cursor's built-in orchestration rather than adding CLI wrappers.
Do not mix host mechanisms unless the user explicitly wants cross-host work.
If edit isolation is needed, read references/worktrees.md before creating or reusing a worktree.
Shared Workflow
- Define the goal and evidence required for acceptance.
- Split separable outcomes into bounded worker tasks; keep dependent decisions in the main session.
- Choose the host-native worker mechanism and the least-isolated safe checkout.
