orchestrate-mode

Invoke /orchestrate-mode or say "become an orchestrator". The lead agent then dispatches worker subagents for all file edits, code execution, and commits, and only coordinates, reviews, and integrates their output until you exit the mode.

Orchestrate-mode forbids the lead agent from executing any concrete work directly; it only dispatches and reviews workers. Multi-agent-mode lets the lead agent still work directly while delegating helper slices to subagents.

Yes. On Claude Code it uses the Agent tool with worktree isolation for workers. On Codex and other runtimes it inspects the actual worker contract to determine whether workspaces are isolated or shared before dispatching.

At most 3 parallel workers without explicit user confirmation, and recursion is limited to depth 1 so workers cannot spawn their own workers. Code-changing workers on a shared filesystem are serialized unless write scopes are disjoint.

A consolidation worker generates patches from each prior-wave worktree, applies them to the main repo, fixes cross-scope coupling, and reruns codegen before the next wave spawns, since fresh isolated workers cannot see uncommitted changes from earlier waves.

Avoid it for ordinary factual questions, which the agent answers directly, and for tasks where the lead agent should still implement some work itself. Use handoff instead when transferring the whole task to a fresh session as an artifact.