Working with it

The row menu

Right-click a row for the Hub first, then where its session lives and what can start beside it, with the ways of keeping it quiet under Quiet and the rarer things under More.

Right-click a row in VS Code: the Hub first, then where the session lives and what starts beside it, then the quiet and the rare entries behind their submenus.

The entries

The first entry is always the Hub. Below it come the entries that depend on where the session lives: a session LampBoard has no terminal into has Show in VS Code, or Show in the Claude app, and a conversation open in VS Code has Move to LampBoard….

EntryWhat it does
Open in the Hubthe session in the Hub, its terminal at the centre. ⌘ click does the same, on every row, here or on another machine
Show in VS Code, or Show in the Claude apponly for a session LampBoard has no terminal into: brings up the window or the app it lives in
Move to LampBoard…on a conversation open in VS Code: takes it up in tmux on this Mac, in its own terminal in the Hub, with everything it remembers, so VS Code can stay closed. See the Hub
Start a new session in this folderstarts a session in the row's folder, on the row's machine, in tmux
New conversation in VS Codea new conversation in the editor's window for that folder
Rename…the name the panel shows, by folder. The session, its window and its folder keep their own names; leave the field empty to go back.
Hidecollects the row into the summary line, which still lights up when the row needs you
Quiet ▸the three ways of keeping one session quiet
More ▸everything else

Quiet

Don't alert me silences the notifications for that project and not the colour. It appears once notifications are on.

Don't blink stops the movement and not the colour, on a row that is asking. Amber in peripheral vision is impossible to ignore, which is exactly what it is for, until you are working next to a session that has been waiting half an hour and you do not intend to answer yet.

Focus on this session puts it in the foreground and pins its row: while it is there the other sessions' alerts wait, and one notification says what waited when the focus comes off.

More

EntryWhat it does
Open without marking as readthe same as ⌥ click
Mark as unreadremedies one click too many, on a row at rest
Move up, Move downthe drag, in words
Show in Finderopens the project's folder
Add a project rule for “repo”…one line every session in that repository keeps to
Project rulesthe rules already there; choosing one takes it off
Copy “claude attach …”for a session started with claude --bg: copies the command that reopens it in a terminal
Use Sonnet until the window resetson an Opus session (Haiku on a Sonnet one), with the helper

Show in Finder and the project rules are not offered for a session on another machine.

Project rules

Add a project rule for “repo”… appears on a row whose session works in a git repository. It asks for one line, such as "every timestamp is stored in UTC", and every session working in that repository reads it with its next prompt, through the helper, as context the model gets and you do not see. A repository holds at most twenty. Project rules lists them; choosing one takes it off, and a session that was told about it is told it no longer applies. lampboard decide, decisions and undecide do the same from a terminal.

A lighter model until the window resets

Use Sonnet until the window resets (13:10) lowers that session one model from its next turn until the five-hour window comes back, then lets it go back on its own model. Choosing it again gives the model back sooner. Never offered for the session in focus, and it needs the helper. See usage left.

A conversation inside a project

Open a project that holds several sessions and each conversation gets a line of its own, with a shorter menu: Open in the Hub, Move up, Move down, Rename this conversation…, and two that are only there:

Remove this row is for a conversation that should not be there any more: a session that is somehow still on disk but that you cannot reach, reopen or close. It is not the same as hiding. A removed line is gone, and if that session ever speaks again it comes back on its own, which is the difference between cleaning up and forgetting. The register of removed lines survives restarts, so one does not quietly reappear three seconds later.

End this session… asks first, and names what it is about to end: the process and when it started. It acts only when the panel can find a live process for that session and prove it is the right one: it matches the recorded process identifier and its start time, so a number reused by an unrelated process cannot be killed by mistake. A Codex conversation has no process of its own to end, and the panel says so rather than ending the one they all share. It sends a polite termination signal, the same one a window close would send, so the session gets to write out what it was doing.

To empty the whole column at once, Clear the list is in Settings › About & help. It asks first, and each session comes back with its next signal.