Teams

A team is more than a list of agents. It's a routing default, a shared memory scope, and a Queen Bee that knows how to coordinate the group.

You've already seen the four starter Hives in Teams (Hives): Product, Sales, Marketing, Operations. This page is the Agent Builder's perspective on the same concept: how teams work mechanically, and how to compose your own.

What a team gives you

When you bundle a set of agents into a team:

• Queen Bee routes within the team first - tasks assigned to the team go to the team's specialists before falling back to general routing.
• Memory is shared inside the team (by default) - agents pick up where other team members left off, without you copy-pasting context.
• Default tool access aligns - a Product team's Developer gets GitHub access by default; a Marketing team's Content Writer gets the connected CMS.
• You assign the team to projects rather than re-picking agents each time.

Composing a team

Open Admin → Teams and click + New team. Fill in:

• Name - what your team calls it.
• Description - what kind of work this team handles, used by Queen Bee for routing.
• Roster - pick one or more agents per role.
• Lead (optional) - designate a specific agent (usually a PM or Manager) to be the team's coordinator.
• Tool access overrides - extend or restrict tools at the team level.
• Memory scope - share memory across the team, or keep agents isolated.

You can also clone a starter Hive as the basis for a new team. Most custom teams in the wild are variants of the built-ins.

📸 Screenshot: the team composition page with a roster of agents and team-level settings.

Team vs. project

A common point of confusion:

• A team is a group of agents. Define once, use across many projects.
• A project is a unit of work. Has one assigned team (or none - agents can be assigned individually).

The same team can be assigned to multiple projects. The same project always has at most one team.

When to build a custom team

Three signals:

• You're consistently assembling the same roster of agents across multiple projects.
• You want a named team to anchor an initiative - "the Q3 launch team."
• You want per-team memory isolation - security-sensitive work that shouldn't leak into other agents' context.

If none of those apply, the starter Hives are probably enough.

Teams in admin vs. teams as Hives

In the docs, "Teams" and "Hives" are interchangeable terms. The Admin → Teams page is where you manage them; the Teams (Hives) section of the docs is where you read about the four starters from a user perspective. This page is the builder/admin angle.

What's next

You now have every layer of Agent Builder. To see how all of it gets deployed against shipped work, head to Deployment.