Docs/The board (Director)/Session lifecycle
Director

Renaming, resuming, and restoring sessions

3 min read

Sessions have a life after you start them: they get named, they survive restarts, old conversations get picked back up, and eventually they get closed. This page covers the small set of moves that manage that life.

Naming

The rename dialog appears automatically the moment a session is created - name it while you still remember why it exists. Rename any time later from the session's right-click menu. Good names carry the fleet: they are what you see on the board, on your phone, and what Car Mode speaks out loud.

Resuming an old conversation

Type /resume (or /continue) in the prompt bar to pick a previous conversation in this repository and continue it - the agent comes back with its history instead of starting cold. The picker lists each resumable conversation with when it was last touched.

Re-linking (recovery)

A session row on the board points at an underlying conversation transcript. If that pointer is ever wrong - say, after moving things around by hand - right click the session and choose Relink Session: it lists the transcripts found for the repo (with message counts and summaries) and lets you point the row at the right one. You will rarely need this; it exists so a confused row is a two-click fix instead of a lost conversation.

Closing

Close a session from its right-click menu when its work is merged and done. If you close the whole Director window while sessions are still running, it asks first - Close Sessions shuts them down cleanly with a progress bar, or Cancel keeps working. Remember the split: closing the Director window only closes the viewer if the Gateway is running your sessions.

Tip
From the phone, the same lifecycle verbs live in the manage bar - back, Snooze, Remove - see working with sessions from your phone.
Note
Restarting the machine? Sessions come back per the lifecycle rules; resume what needs history with /resume.