Team Management

Team Management

A Team consists of 1 Team Leader + N Workers. The Team Leader is a special Worker with management skills that handles task decomposition and assignment within the team. Manager delegates tasks to Team Leaders, not directly to team workers.

Quick Create

# 1. Create each Worker CR with worker-management, then reference them
agt create team \
  --name <TEAM_NAME> \
  --leader-name <LEADER_NAME> \
  --workers <w1>,<w2>

# 2. @mention the Leader in Leader Room to assign task

The Team command fails if a referenced Worker does not exist. Configure model, runtime, image, resources, identity, skills, MCP, channel policy, and lifecycle on each Worker CR. After Team reconciliation, @mention the Leader in the Leader Room; the Leader will coordinate referenced workers in the Team Room.

Full workflow: read references/create-team.md

If admin asks for CPU or memory requests/limits, update Worker.spec.resources. Changing resources recreates that Worker's container, so confirm it is not mid-task.

Gotchas

• Team Leader is a Worker container — same runtime, but with team-leader-agent skills instead of worker-agent skills
• Team workers only talk to their Leader — their groupAllowFrom has [Leader, Team Admin], NOT Manager
• Manager only talks to Team Leader — never @mention team workers directly
• Team Room includes Team Admin — it's Leader + Team Admin + all team workers (no Global Admin unless they are Team Admin)
• Leader Room is standard 3-party — Manager + Global Admin + Leader (same as regular worker room)
• Leader DM is Team Admin ↔ Leader — for team-level management
• Team Admin defaults to Global Admin — if --team-admin not specified
• Delegated tasks use --delegated-to-team — so heartbeat knows to check with Leader, not workers
• Team never owns Worker runtime configuration or lifecycle — update the referenced Worker CR directly

Operation Reference