ModelRefs / Orchestrator Agent — AI Glossary
Orchestrator Agent — AI Glossary
A top-level agent responsible for decomposing a goal into sub-tasks and delegating them to specialist worker agents.
Overview
The orchestrator maintains the task plan, manages handoffs, aggregates sub-results, and decides when the goal is complete. It typically uses a frontier reasoning model while workers can use cheaper specialist models.
Reference details
| Topic | agents |
|---|---|
| Last reviewed | 2026-06-24 |
Related terms
Commonly confused with
Also just called the orchestrator, and not to be confused with a router: a router chooses a destination and stops, while this decomposes a goal, delegates to worker agents, and decides when the goal is met. The difference that matters operationally is that it holds state — it has to recognise a returned sub-result as incomplete and decide what follows, so it needs its own step budget and stopping condition, and a multi-agent system without one is a cost problem waiting to happen. Outside this field "orchestrator" usually means a workflow or container scheduler, which is a different thing entirely.
Continue your research
Use these connected ModelRefs sections to compare alternatives, inspect implementation paths, and review the evidence and governance boundaries relevant to Orchestrator Agent — AI Glossary.
Frequently asked questions
What is Orchestrator Agent?
A top-level agent responsible for decomposing a goal into sub-tasks and delegating them to specialist worker agents.
What concepts are related to Orchestrator Agent?
Closely related concepts include multi agent, handoff, agent.