Agents become teams
Agents now carry a role, a work mode, and a team — so a deployment reads as an org chart: one Lead you brief, its specialists doing focused work. A new Teams view makes it visible.
One agent wired to a dozen skills is a blunt instrument — it does everything passably and nothing
sharply. Real work divides: someone owns the pipeline read, someone owns the follow-ups, someone owns
proposals. This release (v1.42) makes that division first-class. Agents now form teams.
Role, mode, team
Every agent carries three grouping fields:
role—leadorspecialist. The Lead is the one you talk to; specialists do focused work.agentType—mission,workflow, oroperational. The work mode the agent is built for.team— the team it belongs to.
A team is exactly one Lead plus its specialists, grouped by a shared team slug. You brief the
Lead in plain language; it decides what matters, routes work to the right specialist, and assembles
their output into something a human can act on in two minutes.
# workspace/<org>/agents/revenue-lead.yaml
slug: revenue-lead
name: Revenue Lead
active: true
role: lead
agentType: mission
team: revenue-operations
# workspace/<org>/agents/pipeline-analyst.yaml
slug: pipeline-analyst
name: Pipeline Analyst
active: true
role: specialist
agentType: operational
team: revenue-operations
npm run workspace:apply # the team appears once the workspace version lands
The "sub-agent" is retired
Specialists aren't anonymous helpers buried inside one agent's config anymore. Each is a full agent in its own right — its own prompt, skills, evals, and connector access — that happens to sit on a team. That's the whole point: a specialist you can inspect, eval, and permission independently is a specialist you can trust with real work.
See the org chart
The new Teams view (/dashboard/teams) renders each team the way you'd draw it on a whiteboard:
the Lead as your point of contact, its specialists in a grid below — each showing its skills and status.
It's the fastest way to see who's on a deployment and who owns what.
This is the layer the rest of the product rides on. A Mission is open-ended work a team takes on; a Lead is the one that coordinates it. Teams give that coordination an org chart to run against.
See Teams for the full authoring reference.