Supervisor
Place a coordinating agent above a set of specialised agents and route work to them.
Problem
A single agent trying to handle every request type has either too few tools — which limits what it can actually do — or too many, in which case the model gets confused about which tool fits which request, the prompt balloons, and recall drops. The team cannot tune the agent for billing without making it worse at sales. A flat router that just dispatches to a one-shot specialist does not give each lane the multi-step loop it needs. Some coordinating layer above the specialists has to own dispatch and aggregation.
Solution
A supervisor classifies requests and dispatches them to a specialised agent. Each specialist has its own prompt, tools, and possibly its own model. The supervisor may receive results back and decide whether to escalate or respond.
When to use
- Different request types want their own loop, prompt, tools, and possibly model.
- A flat router would be too coarse because lanes need their own multi-step behaviour.
- A coordinating layer can dispatch and decide whether to escalate.
Open the full interactive page →
Diagram, neighbourhood map, code examples, related patterns and full provenance.
Related
- Routing
- Orchestrator-Workers
- Hierarchical Agents
- Blackboard
- Lead Researcher
- Inter-Agent Communication
- Role Assignment
- Swarm
- Hero Agent
- Handoff
- Mixture of Experts Routing
- Conversational Multi-Agent
- SOP-Encoded Multi-Agent Workflow
- Chat Chain
- Dynamic Expert Recruitment
- Outer-Inner Agent Loop
- Cross-Domain Enterprise Agent Network
- Actor-Model Agents
- Group-Chat Manager
- Role-Typed Subagents
- Orchestrator as Bottleneck
- Supervisor-Plus-Gate
- Contract Net Protocol
- One Tool, One Agent
- Magentic-One Generalist Multi-Agent
- Coalition Formation
- Joint Commitment Team
- Distributed Constraint Optimization