What it is
One AI agent can handle one task. Real work often needs several at once: one fixing a bug, another writing tests, a third updating documentation. Agent orchestration is the layer that manages them. It launches agents, hands out tasks, keeps their work from colliding and gathers what they produce so a person can review it.
Think of a kitchen. The cooks do the cooking, and the head chef decides who makes what, in what order, and what leaves the kitchen. Orchestration is the head chef.
What it does
Typical jobs include:
- Assigning work. Splitting a goal into tasks and sending each to an agent.
- Isolating work. Giving each agent its own copy of the files or its own agent sandbox so two agents do not overwrite each other.
- Passing information. Moving results from one agent to the next, and deciding what each one needs to see in its context window.
- Supervising. Tracking progress, retrying failures, enforcing limits on time and spending, and stopping an agent that goes wrong.
- Merging. Combining results and presenting them for human review.
Orchestration and the agent harness
An agent harness runs a single agent's loop: it calls the model, runs its tool calls and manages its memory. Orchestration sits above that and coordinates many harnesses. The two ideas overlap in small systems, but they answer different questions: how does one agent work, and how do several agents work together.
Why it matters
When you run more than one agent, the hard part stops being the model and becomes management. Without orchestration, agents duplicate effort, conflict over shared resources and leave you reviewing a pile of unrelated changes. Good orchestration also gives you one place to apply rules, watch costs and use an emergency stop such as an AI kill switch.
Orchestration is the practical side of a multi-agent system, and it is a core part of agentic coding when several coding agents work on one project.