Reading the column
Anatomy of a row
Five cells, each answering a different question, and a second line that says what the session is doing now.
A row is one project. Everything on it is there because it answers a question you would otherwise have to open a window to answer.
- the lamp what this project's most urgent session is doing
- the ring how much of the context window is spent, and which model
- the name the folder, or the name you gave it
- the slot elapsed time, a clock time, or why a turn died
- the grip drag to reorder; its colour is the agent
The lamp
The state of the most urgent session in that project. Six colours, and only one of them blinks. The six lamps is the page for this.
The ring
How much of the model's context window that session has spent, and which model it is. It is deliberately grey: the lamp already owns the colour on this row, and a ring that turned red near the end would arrive as a second voice at exactly the moment the lamp matters most. The context ring explains the four marks it can carry.
The letter also tells two rows apart when one is Claude Code and the other is Codex, which costs no pixels and no second glyph.
The name
The folder the session runs in, or the name you gave the row yourself. Renaming changes what the panel shows and nothing else: the window is still found by its title, the folder keeps its name.
Beside the name, a few marks: ⚠ when two live sessions wrote the same file in the last two hours, ✉n when two or more answers nobody has read are waiting, and, while the session waits for you, how many minutes its prompt cache stays warm.
The second line
In the wide panel, under the name, one line says what the session is doing now in the fewest words that say it: the command it asks to run, the tool it is running, why it stopped, the first line of the answer that waits, what it is paused on. A session on another machine starts it with @ and the machine's name, a background session with "background". The card says all of it at length; this is the phrase worth reading without moving the pointer.
When the panel holds a permission for that session, it opens under the row, with Allow and Deny. See what it asks for.
The right-hand slot
It does not always show the same thing, because the useful information is not always the same.
| State | What you see | Why |
|---|---|---|
| working, paused | 42m, 7h | On a running session what counts is how long. 7h reads in half a second; 08:14 has to be computed. |
| stopped | rate limit, auth, billing | What counts is why it died, not when. |
| everything else | 14:49, 1d, 3d, 22/07 | The time of the last activity. |
The thresholds reason in calendar days: at half past midnight, an event from ten to midnight is yesterday, so 1d, not "forty minutes ago". The full sentence is always in the card.
Clicking a row does not update that timestamp. It records the agent's activity, not yours.
The grip
Drag it to move the row. Its colour says which agent the session belongs to: terracotta for Claude Code, teal for Codex. It sits two hundred points away from the lamp, which is what makes a second colour affordable there and nowhere else on the row.
The badge
A small mark next to the name.
×3is the number of subagents working inside that session. It explains why the row is yellow, or blue once the parent turn has stopped and only the agents are left.3is the number of sessions collected into that row.
The first wins when both apply.