Team Map

See your agents, the links between them, and the work flowing across.

A list of links tells you that A can talk to B. It does not tell you that the review request went out an hour ago, bounced through two agents, and is now waiting on the one whose context is nearly full.

The Team Map draws the shape of the collaboration, then narrates it.

The Team Map with three linked agents and a recent-activity rail stitching deliveries into chains

Where to find it

  • The default Map view inside Mission Control, above your terminal grid.
  • A Team Map tab in the Orchestration Dashboard.

Both render the same graph. The map loads on demand and never mounts a terminal to draw a node, so opening it does not slow the workspace.

Reading the graph

Terminal cards carry:

  • The agent logo and terminal name
  • Live status
  • Context usage
  • The latest prompt

Edges carry their permissions — send/ask — and pulse green as a message is delivered. A live handoff is visible without reading any terminal output.

The Team Map showing a green pulse as one terminal delivers a message back to its peer

Building the graph by hand

You do not have to create every link through a mention.

  • Drag one terminal card onto another to link them. A confirmation step runs first.
  • Click an edge to manage or unlink it.
  • Click a card to jump to that terminal.

Zoom, re-center, and auto-fit are in the map header. Manual node positions are remembered per project, so a layout you arranged survives the next session.

Recent activity

The rail on the right stitches individual deliveries into chains:

claude → codex → fable → claude

The newest hop pulses while it waits. Open a chain for its per-hop timeline, or copy it as text — useful for pasting the actual review path into a PR description.

The counter in the rail header is the number of retained activity entries, not the number of open requests. For "who owes whom an answer right now", use the Mission Control counters.

What a finished collaboration looks like

Codex ran a review and flagged 27 issues, four of them blockers. Fable verified every file-and-line claim against the source, fixed all 27, and delivered a disposition report back to the reviewer terminal.

A finished cross-agent review: 27 issues flagged, all 27 fixed, delivered back to the reviewer terminal

Nothing in that loop was copy-pasted by hand.

Orchestrations tab

The Orchestration Dashboard's Orchestrations tab lists projects running linked terminals with their participants, live link count, replies awaited, and a View map action.

Before, a project with three collaborating agents looked idle in that list.

Next