Orchestration hands a whole plan to one lead agent, and that agent runs a team. It starts an implementer for every task that is ready, has a reviewer check each one before it lands, and finishes with critics who look over the combined result. Several tasks move at once, and you follow the plan page instead of steering one conversation through every step.
It only starts when you ask for it.
The Orchestration tab: agents working, tasks done, and each task's status in order.
Turn it on
Open Agent features (under More in the sidebar), pick the computer your agents run on, and switch on Orchestration under Tracking & automation. It works with Claude Code. That computer does all the work, so a plan of many tasks keeps it busy for a while.
Click How it works on the card for what it adds and a request to try.
Ask for it
Say it in the conversation, in your own words:
"Make a plan for the settings redesign, then orchestrate it."
"Orchestrate the webhook retries plan."
"Orchestrate the rest of the billing plan, two tasks at a time."
"Stop after the first wave so I can look at it."
If there is no plan yet, ask for one first and read it over. The plan is where you shape the work: its goal, its tasks and what depends on what.
How the work moves
Eight tasks in three waves. Each wave starts the moment the work it depends on is done.
In waves. Every task whose dependencies are done starts at once, each with its own implementer. As those finish, the next tasks unlock.
Each in its own copy. Every implementer works in a separate copy of your repository on its own branch, so agents running side by side never touch each other's files. Finished work merges back once it passes review.
A reviewer's verdict decides each task's path. After a few failed rounds, the lead agent asks you instead of looping.
Reviewed before it lands. A reviewer checks each finished task against what the task asked for and passes it, sends it back with notes, or rejects it. The lead agent tries a task a few times at most, then stops and asks you.
Critics look at the whole result, not single tasks. Serious findings go back in as a new wave.
A final sweep. Once every task has passed, critics review the combined code. Anything serious becomes new fix tasks and another wave. When they find nothing serious, the plan is done.
Follow it on the plan page
Open the plan. Its tasks move from Open to In Progress to Done as agents pick them up and finish, and the progress bar under the goal fills in.
Orchestration shows how many agents are working, how many tasks are done and any that are blocked, the Active Sessions with a link into each, and a Task Timeline with every task's status.
Graph draws what depends on what, so you can see which tasks are waiting on which.
Overview keeps the plan's timeline: progress at the end of each wave and the decisions the lead agent made, so the reasons survive the run.
The Graph tab: finished tasks, the ones running now, and the ones still waiting on them.
The lead agent's own conversation narrates each wave: what it started, what passed review, what it sent back. Message it at any point to change course.
When it needs you, you hear about it. A task the agents can't finish, a rejected review or a missing piece of context comes back as a question, and the lead's conversation is flagged in your inbox as needing you.
Orchestration or a workflow
Choose orchestration when the shape of the work isn't known up front and an agent should work it out. When the steps are known and must run the same way every time, with an approval at a fixed point, use a workflow.
When something is off
What you notice
What to do
The lead agent asks you about a task
Answer in its conversation. It carries on with the rest of the plan meanwhile
Too many agents run at once for your machine
Tell the lead agent to run fewer tasks at a time
A task is stuck in progress
Open the task. Its sessions and activity show where it stopped. Ask the lead agent to retry or split it
The plan's tasks look wrong before it starts
Edit the plan first, or ask for a new breakdown. Orchestrating a bad plan builds the wrong thing faster