Orchestrator
- Agents
- Standard term
An orchestrator is the controller that coordinates the other parts of an AI workflow. It decides what runs in which order, assigns each task, passes results along, and handles a failed step by retrying, stopping, or using a backup.
The controller needs enough state to know which work is ready and what depends on it. Recording task assignments, results, and failures at handoffs makes missing or incomplete work visible. Coordination may be handled by one controller or shared across components.
Where you’ll meet it
Your team's AI research tool hands each question to three helper agents, often called “subagents.” One searches the web, one reads your company's documents, and one writes the report. Today's report cites only websites, and the run history shows the document helper timed out and the tool wrote the report without it.
What to do
Ask for the missing document search to be rerun before relying on the report. Send the timeout record to whoever maintains the tool, and ask them to make required sources block completion or clearly mark any report produced without them.
Easy to mix up
| Orchestrator | Subagents |
|---|---|
| Coordination and handoffs across the work | A delegated part that reports results back |
Check yourself
An orchestrator uses an AI model to route incoming email. Shipping notices make up half the mail and come from a dedicated, verified warehouse address used for no other mail. The model misfiles some each week. Which change makes this route more reliable?
Go deeperAn orchestrator can be fixed code, a model, or a mix
Anthropic's 2024 guide "Building effective agents" separates workflows, where code sets the path in advance, from agents, where a model directs itself. In its orchestrator-workers pattern, a model splits each task into parts at run time and hands them to workers. Many tools in everyday use combine the two, with code fixing the overall order and a model planning the steps inside a stage.
Handoff records help locate a failure. If a worker’s permissions or validation checks caused it, repair them there; the orchestrator may also enforce checks at the handoff. A correlation ID, one ID carried with each case through every part, lets you trace a request across the run.
Sources
- Building effective agents, Anthropic
- MCP Security Best Practices, Model Context Protocol