The Fleet Map
4 min read
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.
Four 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:
- By machine - sessions grouped under the computer they run on, and the Director on it. Best for "what is running on that box".
- By repository - sessions grouped by the repo they are working in. Best for "who is touching this project".
- By agent - sessions grouped by which coding agent is driving them. Best for "where am I running Claude Code versus another agent".
- Fleet list - a flat grid of every session, with a legend of the status colors. Best for a plain, complete inventory.
Each card shows the same session number as the rail, 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, and it filters in place - the sessions that do not match drop away, and the ones that remain keep their positions rather than rearranging. Clear the box to bring the whole fleet back.
When a machine cannot be reached
A fleet spread across several computers will sometimes have one briefly drop off the network - a laptop that sleeps, a Wi-Fi blip. 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 - a machine that has just become unreachable. Its card dims and reads last seen 20s ago, but it holds its place. Most of the time the machine comes right back and the card returns to normal on its own.
- Offline - a machine that has stayed unreachable. The card stays dimmed and reads last seen with the longer age, so you can tell a real outage from a hiccup.
A normal, reachable machine is simply an undimmed card - 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.