Managing sessions

Press Ctrl+B to open the session browser. It lists every session for the current runtime with a preview, a relative timestamp, the active agent, and badges for anything that needs your attention.

Sessions are attached to a runtime, not a specific sandbox instance. Resetting the sandbox does not erase the session — the transcript and metadata survive. That’s why “continue yesterday’s work” is a reliable workflow.

Status badges surface state the sidebar can’t otherwise show:

Badge	Meaning
active	The session you’re currently on
running	Agent is working right now (a background session keeps going)
approval	A permission prompt is waiting for you
input	The agent is waiting on text input
failed	The last turn errored
N unread	Events landed while you were on a different session
N queued	Messages you typed that the agent hasn’t gotten to yet
stale	Reconnect state needs replay

Use the browser to:

• pick up an older thread — ↑/↓ to highlight, Enter to open
• start a fresh one — press n
• delete a session you no longer want — press d
• find a specific thread — type to search across title, preview, agent, and session ID

The browser never steals focus. A background session that needs input shows approval or input in its row and waits for you to switch into it.

Session commands

Most session management is a slash command away:

Command	Effect
/new	Start a fresh session with the current agent
/reset (/clear)	Wipe the current session’s transcript and keep going
/rename <title>	Give the session a recognizable title
/export [filename]	Write the transcript to session-<id>.md (or the filename you pass)
/compact [guidance]	Summarize older history to shrink context before continuing
/sessions	Open the browser (same as Ctrl+B)

The auto-derived title is usually the first user message, truncated. Rename once the thread has a direction so you can find it later.

Compacting a long conversation

As the transcript grows, you’ll start bumping against the model’s context window. /compact asks the agent to summarize older turns into a single message and keeps going on the same session.

/compact focus on what we've tried and what worked

Compaction is non-destructive — older messages are marked compacted rather than deleted, and the session keeps its runtime attachment. Nothing downstream breaks. See Compaction for how to shape the summary.

Note

Compaction is the right reach when the conversation has been productive but long, and you want the agent to stay oriented. If the thread has drifted off, /new is usually better — start clean with a focused prompt.

Queued messages

Messages you type during a turn travel with the session — switch threads and they stay waiting, not lost. For how the queue behaves in the composer, see Conversation.