Skip to main content

Sessions

PreviewAvailable on: WindowsShips in the preview channel only. Not a stable release.

Resume, fork, attach, detach, stop, and quit — six verbs that are frequently confused.

A session is a durable conversation with an agent, owned by the daemon. Your terminal is a view onto it. Getting the six session verbs straight prevents most accidental work loss.

The six verbs

CommandEffect on the sessionEffect on your terminal
/attachConnects you to an existing sessionShows it
/detachKeeps it runningReleases your terminal
/resumeReconnects to the most recent paused sessionShows it
/forkBranches a copy from the current stateShows the branch
/stopCancels the in-flight turnStays attached
/quitDetaches all sessions and exitsCloses

IMPORTANT

/detach and /stop are the pair people confuse. Detach leaves the agent working and gives you your terminal back. Stop cancels the current turn but leaves you attached. They are close to opposites.

Detaching is the normal thing to do

If an agent is doing something that takes minutes, you do not have to sit and watch:

/detach

The turn continues in the daemon. Come back with:

/resume

Or attach to a specific session:

/attach <session-id>

Forking

/fork branches from the current conversation state, which is useful when you want to try a second approach without losing the first.

TIP

Fork before a risky instruction, not after it goes wrong. Forking preserves the state you had at the fork point; it cannot recover a state you already talked past.

Sessions survive more than you expect

Because the daemon owns them, sessions survive:

  • Closing the TUI
  • Closing the desktop
  • Closing the terminal
  • Rebooting the machine

They do not survive being explicitly stopped, and they do not survive past their retention window.

Verify what exists:

nala sessions list

Clearing versus compacting

CommandDoes
/clearClears the composer
/compactSummarizes and compacts the conversation to reclaim context budget

Compacting is lossy by design — it trades detail for room. Do it at a natural boundary.

Common recovery

SymptomCauseFix
Session missing after restartStopped, not detachedNothing to recover; check nala sessions
/resume finds nothingNo paused session for this workspacenala sessions to list what exists
Attached but the transcript is emptyReattached to a fresh sessionCheck the session id in the header
Turn will not cancelProvider is not responding to cancellation/stop, then check the provider pane