Coordinator Mode
Published Updated
What is Coordinator Mode?
Coordinator Mode is Orbit’s way of running a large build as parallel subtasks, each in its own Git worktree, with a reviewed plan going in (Gate 1) and a claim-by-claim review of the results coming out (Gate 2).
A mode for running complex multi-phase builds as parallel subtasks with human review gates. Decomposes a large task into independent worktrees.
When you decompose a large task with `orbit_decompose`, Orbit breaks it into independent subtasks and assigns each to a separate git worktree. Gate 1: review and approve the plan before any code is written. Gate 2: review the full diff before merging back to main. Coordinator Mode shows cost estimates upfront and prevents merge conflicts by isolating subtasks until ready.
How it relates to Orbit
Orbit decomposes a larger request into agent work and reviews it at two gates. See Coordinator Mode for details.
When you would use it
You use Coordinator Mode for complex tasks too large for a single prompt — typically multi-phase builds where the parallel speedup justifies the planning overhead.
Common operations
- Building a feature with multiple independent components in parallel
- Refactoring across multiple modules where subtasks don't conflict
- Any large task that benefits from decomposition
Frequently asked questions
When should I use Coordinator Mode?
For work too big for one prompt that splits into independent pieces, such as several features touching different parts of a codebase. See Decompose a Build with Coordinator Mode.
Where do the subtasks land?
On an integration branch, after Gate 2 checks what each subtask actually delivered. See Coordinator Mode.
Related terms
Dashed terms are named in the source but do not have a page here yet.
Where this is taught
No learning path uses this term yet. Browse the Learning Atlas for guided sequences through related ideas.