What is Team Lead Agent?
Also called supervisor agent, orchestrator agent.
A team lead agent is an agent whose job is coordinating other agents: interpreting an incoming request, deciding which specialist should handle it, passing along the context that specialist needs, and assembling or checking the result. It performs little of the underlying work itself. The pattern is also called a supervisor or orchestrator, and the three names are used interchangeably.
The lead exists to keep routing decisions in one place. Without it, every agent needs to know about every other agent, and the arrangement becomes difficult to change safely. With it, adding a specialist means updating one set of routing instructions. This is the same reason human teams centralize intake rather than sending every request to everyone at once.
A lead typically holds the request queue, the roster of available specialists and what each is for, the rules about what requires human approval, and the record of what was done. Making the lead the single point of contact for people is common, because it gives one place to ask for status and one place to read the history afterwards.
The lead is also where risk concentrates. A routing mistake sends work to the wrong specialist with the wrong context, and a lead holding broad permissions inherits the reach of everything beneath it. Keeping its own instructions short, its direct tool access minimal, and every routing decision logged is what keeps the pattern debuggable.
The lead is the coordinating element of a multi-agent team. In products modeled on an organization chart it is often presented as a manager role. Where the sequence of work never varies, a fixed pipeline or a plain workflow is simpler and more predictable than a lead agent making the identical decision every time.
Key points
- Coordinates other agents rather than doing the work
- Holds routing rules, the roster, approvals, and history
- A single point of contact simplifies status and audit
- Concentrates risk, so keep its access and instructions minimal
In practice
A small agency routes everything through one lead agent. A client email arrives asking for an updated timeline and a quote for extra work. The lead recognizes two separate requests, sends the timeline question to the agent with project system access and the quote to the pricing agent, waits for both, assembles one reply, and holds it for the account manager to approve.