AutoAgentBuilder lets you build the team per ticket, at request time.
Overview
Step 1: The naive approach and why it breaks
A fixed roster forces every ticket through the same specialists:Step 2: Build the team from the ticket
ConcurrentWorkflow is the right structure here: the specialists examine the same ticket from different angles and do not depend on each other’s output.
Step 3: Scale the team to severity
num_agents is the dial. A password reset does not deserve five specialists; a production outage does.
With
num_agents=1 the builder returns a single well-scoped generalist rather than refusing. The default prompt explicitly states that a lone agent is a correct answer for a single-skill task.Complete Example
Controlling cost
Every triage call makes one builder request plus one request per specialist. Two ways to keep that in check: Use a cheaper builder model. Roster design is easier than the analysis itself:Use Cases
- Support triage — specialists matched to each ticket’s actual domain
- Incident response — team scaled to incident severity
- Content moderation — reviewers chosen by the kind of violation reported
- Code review — reviewers picked from what a diff actually touches
- Lead qualification — analysts matched to industry and deal size