The Fleet Map

The Fleet Map is the whole fleet seen at once. Where the rail is a list, the Fleet Map is a picture: a canvas with a root Gateway node that branches out to panels of session cards, joined by connectors, each card carrying a status dot. It answers "what is my whole fleet doing right now" in one look. Open it from Fleet Map in the left navigation.

Eight ways to group the fleet

A row of pivots at the top right re-groups the same sessions along different lines - pick the one that matches the question you are asking. The map remembers your choice, so it reopens on whatever grouping you used last.

• By machine - sessions grouped under the computer they run on, then under each Director on it. Best for "what is running on that box". A Director with no sessions still shows: as a free slot when it is reachable, or labeled as one that is not running or cannot be reached when it is not.
• By director - one panel per Director across the fleet, headed by the Director's name with its machine underneath. Best when one machine runs several Directors and you want them side by side.
• By repository - sessions grouped by the repository they are working in, so every worktree and clone of one repository rolls up together. Best for "who is touching this project".
• By working tree - sessions grouped by the on-disk checkout folder, so each worktree stands alone. The companion question to By repository: not "which project" but "which checkout".
• By agent - sessions grouped by which coding agent is driving them. Best for "where am I running Claude Code versus another agent".
• By model - sessions grouped by the model each one is actually running, one step below By agent: not "which tool" but "which brain in that tool". A session whose model is not known sits in its own named lane rather than disappearing into the others.
• Fleet list - a flat grid of every session, with a legend of the status colors. Best for a plain, complete inventory.
• Missions - the fleet grouped into missions, each card carrying the why of the work, with sessions that belong to no mission counted as standalone. It is a wall of mission cards rather than a lane layout, and while it is active the count line at the top reads missions and standalone sessions instead of machines and repositories.

A card shows the same session number as the rail - when the session has been assigned one - so a session you know by number is just as easy to spot on the map. Clicking a card opens that session.

Finding a session

The Search titles box filters the map to the sessions whose titles match what you type. It is case-insensitive. The sessions that do not match drop away - along with any panel that goes empty - and the ones that remain keep their order, so the map never reshuffles, though gaps close up as cards drop out. Clear the box to bring the whole fleet back. The box is there on every grouping except Missions - the missions view is not searchable, so the box hides while that pivot is active rather than sitting there dead.

When a Director goes quiet

A fleet spread across several computers will sometimes have a Director go quiet - a laptop that sleeps, a Wi-Fi blip. These states belong to the Director, not the machine: one machine can run several Directors, and one of them going quiet says nothing about the others. The Fleet Map is built so that a momentary miss does not make sessions blink out and the whole map reflow. Instead, a card changes appearance in place:

• Wobbly - the Director's connection is up, but nothing recent has arrived, so what you are looking at is going stale. Its cards dim and read last seen 20s ago, but they hold their place, and the Director can still take a new session. Most of the time fresh data arrives and the cards return to normal on their own.
• Offline - the Director's connection is down. It cannot be reached or acted on; its cards stay dimmed and read last seen with the age, so you can tell a real outage from a hiccup.
• Not running - a Director that was shut down rather than lost. Its sessions are shown the same dimmed, dated way - they are the last thing it said - but the label says it is not running, so a deliberate shutdown never reads as an outage.

A normal, reachable Director is simply undimmed cards - there is no "online" label to read. Because entries change in place rather than disappearing, the map stays steady and you never lose track of where a session was.

Where to go next

• Working in a session - open a card and steer the agent.
• Answering agents remotely - the away-from-your- desk flow, and what reachability needs on your network.