Team Agents are the member agents on a team, and the roster where you add, remove, and govern who the Team Manager can route to.

Overview

The Agents section lists the member agents on a team — "Build your team by adding AI agents with different specialized roles." These are the specialists the Team Manager delegates to. Each row shows the Agent Name, Owner, and Last Updated, and an icon to open that agent in a new tab. Clicking a row opens the member agent. The roster is where you add and remove members and set per-member access rules.

Note: Created On and Last Updated By columns are also available, hidden by default — turn them on from the column-visibility control, or hover the Last Updated date for the same detail.

Adding a Member Agent

Use Add Agent to open the picker — Add Agents — "Pick specialized Agents that work together to streamline workflows." Search and multi-select from the agents not already on the team, then Add. You'll see Agents added successfully. Add agents that each cover a distinct area (for example a billing agent, a support agent, and an analytics agent) so the manager has clear specialists to route to.

Removing a Member Agent

Use Remove on a member's row. It asks you to confirm — "Are you sure you want to remove '{name}' from this team? This action cannot be undone." — and detaches the agent from the team. Removing a member from the team doesn't delete the agent itself; it stays available on its own and on any other teams.

Per-Member Governance

Each member has a Governance action that opens its Governance Conditions — a drawer titled with the member's name, holding a filter that scopes when that member agent is used within the team. Build the conditions, then Set to apply them, or Reset to clear the drawer back to empty. Use it to constrain a member to certain conditions (for example, only handle requests that match a particular criterion). Governance is the one per-member setting — the roster doesn't assign explicit order or roles; the manager's instructions, plus each member's own description and governance, determine how work is delegated.

The same conditions drawer appears on an agent's Tasks as Task Governance Conditions — there it gates when a task is available rather than when a member is used. A task with none shows a Set conditions button; once set, the screen summarizes how many conditions are in play.

How Governance Is Enforced at Runtime

Governance conditions are evaluated per conversation, on every manager turn — not once at save time. Before the Team Manager decides where to route, each member's condition is checked against the live context of the session; conditions can reference values produced by the team's prerequisite actions and variables from the deployment the conversation arrived through, so the same team can expose different specialists on different channels or for different users. A member whose condition fails (and any member disabled for that conversation) is simply left out of the manager's delegation options for that turn — the manager cannot route to an agent it cannot see.

Note: If a condition fails to evaluate, the member is excluded rather than allowed.

How the Manager Knows What Each Member Is Good At

From the member's own profile. When the eligible-member list is assembled each turn, every member is presented to the manager by name and described by its description — or, if it has none, by its role and goal. Members with a sharp, distinct description get routed to accurately; members with none give the manager little to reason with. That text, together with the Team Manager Instructions, is the routing logic.

If the Manager Names a Wrong or Removed Member

Delegation is validated. The target is looked up by name among active (non-archived) agents and checked against the team's current roster; if the agent doesn't exist or isn't on this team, the delegation fails safely and the manager is told so — it can re-route or ask for clarification instead of the request silently dying. This also means renaming, archiving, or removing an agent mid-conversation immediately stops it from being routable.