Teams

A team is a named group of members and agents inside a workspace. Teams let you assign tickets at a coarser granularity — "the DBA Team" rather than picking a specific person — and let the team's leader agent handle coordination and delegation.

Teams are the most natural way to mix human and agent labour on the same surface. A "Health-check Squad" might include two on-call DBAs and a DB Guardian agent; when a ticket is assigned to the team, the leader agent evaluates it first and decides who should handle it.

How Teams Work

When a ticket is assigned to a team, the flow looks like this:

1. Assignment — the ticket's assignee becomes the team; every team member can see it in their ticket list, but they do not receive a task notification
2. Leader activation — Mopheus automatically enqueues the team's leader agent to process the ticket
3. Briefing injection — the leader agent receives a team briefing that includes the roster, each member's capability tags, and your team instructions
4. Evaluation and delegation — the leader agent reads the ticket and decides whether to handle it itself or delegate to a specific team member (human or agent)
5. Closed loop — when a member finishes and posts a comment, the leader agent is re-triggered to evaluate the outcome and record its decision

This means: assigning a ticket to a team is essentially activating the leader agent's coordination capability. Human and agent members do not automatically receive tasks; the leader agent dispatches work as needed.

Create a Team

1. Open Teams in the sidebar
2. Click New team
3. Fill in:
   • Name — display name (DBA Team, On-call Squad, Health-check Squad)
   • Description — optional Markdown blurb explaining the team's scope
   • Instructions — optional system prompt injected into the leader agent's context when it processes team tickets. Use this to define how the leader should evaluate, route, or prioritise work
4. Pick a leader agent (required) — you must designate an agent as the team leader; it will be responsible for all subsequent coordination and delegation
5. Click Create

Add Members

A team can contain any combination of humans and agents, but the leader must be an agent.

1. Open the team page
2. Click Add member
3. The picker has two tabs:
   • Members — workspace humans
   • Agents — workspace agents
4. Pick one or more and click Add

There are two roles inside a team:

Roles inside a team are independent of workspace roles — a workspace Admin who is a team Member has no special power inside the team.

Transfer Leadership

Every team has exactly one leader at all times. The leader cannot be removed — you must transfer leadership first.

To change the leader:

• UI: on the team detail page, click the Set as Leader button next to any non-leader member. The current leader is automatically demoted to member.
• CLI: mopheus team member promote <team-id> <member-id>

The transfer is atomic — the old leader and new leader roles swap in a single operation.

Archive and Restore

Archiving soft-disables a team: it no longer appears in the default team list and can no longer be assigned new tickets. All existing assignments and history are preserved.

• UI: open the team, click Archive in the top-right menu.
• CLI:

  mopheus team archive <id>   # soft-disable
  mopheus team restore <id>   # undo archive

Archived teams are visible in the UI when you toggle Show archived, and via CLI with --include-archived.

Assign a Ticket to a Team

Teams are one of the three assignee types.

From the UI: open the ticket, open the Assignee picker, switch to the Teams tab, and pick a team.

From the CLI:

mopheus ticket assign <ticket-id> --team-id <team-id>

When a ticket is assigned to a team:

• The team appears as the ticket's assignee
• The team leader agent is automatically activated to evaluate and delegate
• Team members (including humans) do not automatically receive task notifications until the leader dispatches the work

Team Leader Workflow

When processing a team ticket, the leader agent receives a briefing similar to this:

## Team Roster

Leader (you):
- DB Guardian — agent — `@DB Guardian (agent)`

Members:
- Alice — member — `@Alice (member)`
- Health-check Bot — agent — `@Health-check Bot (agent)`

## Team Instructions

Prioritise urgent production incidents for human members; routine health-check tasks can be assigned to the Health-check Bot agent.

The leader agent then decides:

• action — the leader handles it itself or delegates to a member
• no_action — the leader evaluates and decides no action is needed
• failed — the leader encountered an error during execution

After evaluation, the leader can record its decision via CLI:

mopheus team activity <ticket-id> action --reason "Delegated to Health-check Bot for daily inspection"

Command Line Reference

# List workspace teams
mopheus team list
mopheus team list --include-archived   # include archived teams

# Get team details (includes member list)
mopheus team get <id>

# Create a team (leader agent is required)
mopheus team create --name "DBA Team" --leader <agent-name-or-id>

# Update team info
mopheus team update <id> --name "New Name" --instructions "New team instructions"

# Update instructions from a file
mopheus team update <id> --instructions-file ./team-instructions.md

# Archive / restore a team (there is no `team delete` CLI; archive is the soft-delete)
mopheus team archive <id>
mopheus team restore <id>

# Manage team members
mopheus team member list <team-id>
mopheus team member add <team-id> --member-id <id> --member-type 0   # 0=member, 1=agent
mopheus team member promote <team-id> <member-id>  # transfer leadership to this member
mopheus team member remove <team-id> <member-id>   # leader cannot be removed

# Record leader evaluation decision
mopheus team activity <ticket-id> <action|no_action|failed> --reason "Explanation"