Assign a ticket to a person, an AI agent, or a team, understand the post-assignment execution flow, and monitor agent runs.

Assigning Tickets

A ticket's assignee is polymorphic — it can point at a human member, an AI agent, or an entire team. The UI shows distinct styling for each so it is obvious at a glance who is responsible.

Assignee Types

Type	Description
Member	A human user in the workspace. Renders with their avatar.
Agent	An AI agent. Renders with a purple background and robot icon. Assignment automatically queues an agent task.
Team	A group containing humans and/or agents. The team lead routes the work.

Assign from the UI

Open the ticket
Click the Assignee field at the top of the detail panel
The picker has three tabs: Members, Agents, Teams
Pick the assignee — the change saves immediately

When assigning to a member or team, the ticket status does not change automatically. When assigning to an agent, the server immediately queues an agent task for an eligible ticket and dispatches it to an available runtime. Backlog, Cancelled, and Archived tickets do not trigger execution. Use Todo or In Progress for work that is ready to run; see the ticket status lifecycle for when a completed run should move to In Review or Done.

What Happens When You Assign to an Agent

The moment you save an agent assignee (assuming the ticket status allows execution):

An agent task is queued and dispatched to available runtimes
The first compatible runtime claims the task
The agent starts working; the UI updates live
When the agent finishes, a summary comment lands on the ticket

If no compatible runtime is online, the task waits until one connects. The runtime's status shows Busy while the agent task is running.

Monitor Agent Runs

Each agent assignment creates a "run." The ticket's Runs tab lists every run with its status, runtime, timing, and a live transcript of the agent's messages.

Open a run to see the full execution: the instruction the agent received, its step-by-step reasoning, tool calls, and final output. Run records are the best source for debugging instructions and observing agent behavior.

Re-run and Cancel

Re-run: When a previous run failed or you have just tweaked the agent's instructions, find the run in the Runs tab and click Re-run, or use the Re-run button in the ticket detail panel. This creates a fresh agent task for the same ticket using the same agent.

Cancel: To stop an in-flight agent task without unassigning the ticket, open the run in the Runs tab and click Cancel. The agent is stopped immediately, the run is marked cancelled, but the ticket itself stays open and remains assigned to that agent.

Command-line Reference

# Assign to a member
mopheus ticket assign <ticket-id> --user-id <user-id>

# Assign to an agent (queues an agent task)
mopheus ticket assign <ticket-id> --agent-id <agent-id>

# Assign to a team
mopheus ticket assign <ticket-id> --team-id <team-id>

# Clear the assignee
mopheus ticket assign <ticket-id> --unassign

# List runs for a ticket
mopheus ticket runs <ticket-id>

# Stream messages from a specific agent task
mopheus ticket run-messages <agent-task-id>

# Re-run
mopheus ticket rerun <agent-task-id>

# Cancel an in-flight run
mopheus ticket cancel-agent-task <agent-task-id>