Teams

A Team is a group of agents with one Lead and its specialists. 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. The org chart of a deployment.

Why teams

A single agent wired to a dozen skills becomes a blunt instrument — it does everything passably and nothing sharply. Real work divides: someone owns the pipeline read, someone owns follow-ups, someone owns proposals. Vocion models that division directly.

A Team retires the old "sub-agent" framing. Specialists are first-class agents — each with its own prompt, skills, evals, and connector access — not anonymous helpers buried inside one agent's config. The Lead is the one you talk to; the specialists are the ones it dispatches.

Roles and modes

Every agent now carries three grouping fields:

Field	Values	Meaning
`role`	`lead` \| `specialist`	Whether this agent coordinates the team or does focused work within it.
`agentType`	`mission` \| `workflow` \| `operational`	The work mode the agent is built for — open-ended goal work, structured step sequences, or recurring operational duties.
`team`	any slug	The team this agent belongs to. Agents with no `team` fall under Unassigned.

A team is exactly one lead + its specialists grouped by a shared team slug. You reach the team through its Lead; the Lead runs Missions and Workflows, delegating to specialists as the work demands.

Authoring

Teams are pure workspace config — no code. Set the three fields on each agent YAML under workspace/<org>/agents/:

slug: revenue-lead
name: Revenue Lead
description: Coordinates the Revenue Operations team — triages, assigns, assembles.
active: true
role: lead
agentType: mission
team: revenue-operations

slug: pipeline-analyst
name: Pipeline Analyst
active: true
role: specialist
agentType: operational
team: revenue-operations

Then apply:

npm run workspace:apply      # sync to DB; records a workspace_version row

The applier persists role / agentType / team on each agent row. No migration to write, no restart — the team appears once the workspace version lands.

In the app

The dashboard's Teams view (/dashboard/teams) renders each team as its org chart: 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, at a glance, who's on a deployment and who owns what.

Connection to other resources

Agents — the members of a team; each is a full agent in its own right.
Missions — the open-ended, goal-driven work a Lead coordinates across the team.
Workflows — the structured procedures a team runs.
Skills — what each specialist actually does.