Preview availability
Orchestrate coordinates a lead agent and bounded specialist work. It is a Preview capability controlled in Settings › Labs. The strategies offered depend on your plan, ready agents and the current build's admitted capabilities. A visible strategy is not a promise that every installed agent can fill every role.
Choose a strategy
| Strategy | Intended shape |
|---|---|
| Focused | A focused route for bounded work. |
| Adaptive | Select specialist work as the objective develops. |
| Ensemble | Bring multiple contributions into the result. |
| Overdrive | Use the widest admitted coordination strategy for demanding work. |
The actual assignments and review are the evidence of what ran. Inspect them rather than inferring a fixed number of agents from a strategy name.
Lead, specialists and review
The lead owns the mission's narrative. Specialists receive scoped work and report back. Writing specialists can use isolated working copies; read-only specialists can share the mission checkout. A specialist given Git publication authority can require its own clone.
Independent review checks a contribution through a separate reviewing role. A review result is evidence about that contribution, not a guarantee about every external system or an automatic release approval.
When a route cannot run
An unavailable agent, missing sign-in, plan limit or incomplete route can stop orchestration. Read the reported reason and fix the prerequisite. Partial specialist work may still be useful, but an incomplete orchestration result should not be treated as a completed objective.
The lead is fixed once an orchestrated mission starts. Start a new mission when you need a different lead.