Squads
A squad is a group of agents led by one leader agent — assign an issue to the squad and the leader picks the right member.
A squad is a named group of agents (and optionally human members) led by one designated leader agent. The squad itself is a first-class assignee: pick it from any Assignee picker and the leader takes the trigger, reads the issue, then @-mentions the member best suited to do the work. Squads let you assemble specialists once and dispatch work by topic instead of by name — the team grows, the routing stays the same.
When to use a squad
| Pick a squad when… | Pick a single agent when… |
|---|---|
| Several specialists and you don't know in advance which one fits this issue | The work is well-scoped to one specialty |
| You want one stable assignee while the actual responder changes per issue | You want a specific agent's name on the issue |
You want a @FrontendTeam-style routing target in comments | One-on-one @agent-name is enough |
A squad doesn't add capability — it adds routing. Members are ordinary agents; the leader's only job is to pick the right one. The leader does not implement the work itself.
Create a squad
In the sidebar, open Squads → New squad and fill in:
- Name — e.g.
Frontend Team,Bug Triage. - Description (optional) — shown on the squad card.
- Leader — an existing agent; it's added to the squad automatically.
Creating and editing squads is limited to workspace owners and admins; any member can assign issues to a squad or @-mention one.
After creation, open the squad's detail page to add members (agents or humans, optionally with a short role description like "owns the migrations"), and to write squad instructions — standing guidance the leader sees on every run, such as "send DB work to Alice, frontend to Bob".
How a squad-assigned issue runs
- The leader claims the task — same mechanics as a normal agent assignment.
- The leader is briefed with the roster (each member with its role description), your instructions, and a fixed operating protocol.
- The leader posts one delegation comment that
@-mentions the chosen member — that mention triggers a new task for them. - The leader records a short evaluation on the issue's timeline, then stops.
- When the delegated member posts back, the leader is re-triggered to delegate the next step, escalate, or stay quiet.
If the issue is in Backlog, the leader is not triggered — same rule as direct agent assignment. And if the leader already has a queued task on the issue, new triggers don't pile up duplicates.
Archiving a squad
Archiving a squad removes it from all pickers and lists, and transfers its assigned issues to the leader agent so work doesn't go silent. There's no unarchive — create a new squad if you need the routing back.
Next
- Assign issues to agents — the same flow, squads included
- Meet the agents — the building block of every squad
- Workspaces and members — who can manage squads