What is an agent team?

A team is a small group of agents working under one lead. You delegate one ask; the lead figures out who on the roster handles what, and you get a coordinated result back. It's the shape Claos uses for work that spans more than one specialist.

Think of it this way: an agent is one hire, a team is a small department. The team is the right surface when the work has parts — strategy, copy, design, analysis — that you'd normally hand to different people.

A team is a lead plus a roster

Every team has a lead and a roster.

The lead is one agent on the team, marked with a Lead badge. They hear your request first, decide how to handle it, and either do the work themselves or hand it to the right specialist on the roster. The roster is everyone else — the team's individual contributors.

The lead isn't a different kind of agent. It's whichever agent on the team you've chosen to lead. Reassignable at any time.

When to ask a team instead of an agent

Ask an agent when the work fits one job description — a copywriter for a tagline, a code reviewer for a pull request, a researcher for a fact-check.
Ask a team when the work spans disciplines — a campaign brief that needs the strategist, the copywriter, the designer, and the analyst. Or a launch plan that touches marketing, sales, and operations.

If you find yourself going back and forth between two agents to finish one thing, that's usually a sign you want a team.

What's inside a team

Four things define a team:

Name and description. What the team does, in a sentence.
Business area. One of nine values: Marketing, Legal, Strategy, Accounting, Sales, Engineering, HR, Operations, or Custom. Used to group teams on the Teams page; doesn't affect behaviour.
Lead. The agent leading the team. The first agent you add becomes the lead by default — you can reassign.
Roster. Every other agent on the team. These are the same agents that exist on your Agents page, so a single agent can sit on multiple teams (a daily-briefer that shows up across packs, for example).

How a team does work

In chat. You message the team, and the lead answers first. As they work through the ask, the lead hands parts to the right roster members — you'll see the speaker's avatar and name change to whoever is contributing at each step. The lead wraps up at the end with the consolidated result. From your side, it reads like watching one conversation move across a small group.

On a task. When a team is the assignee on a project task, the lead is who Claos hands the task to. The lead reads the instruction, plans, and coordinates the roster the same way they do in chat. The same AI Schedule controls apply — set Frequency on the task, and the team runs on that cadence. See Scheduling an agent — scheduling a team works the same way.

Tips and gotchas

The lead is your pick, not Claos's. First agent added is the lead by default, but you reassign in the team's Settings any time.
Members don't talk to each other in a side channel. Coordination is lead-mediated — members contribute when the lead hands them the work, or when you @mention them directly.
One assignee per task still applies. Two teams can't share a single task. If the work spans two teams' areas, split it across two linked tasks.
Same agent, multiple teams. Agent definitions live in your workspace, and teams reference them by membership — adding the same agent to a second team doesn't duplicate it.
A team's reach is the union of its members' tools. Integration access is set on each individual agent's Tools & Access list, not on the team — if you want the team to act in Slack or Jira, the relevant agents on the roster need those integrations toggled on. See Giving an agent access to an integration.