Chat history
Past conversations are stored per scope and listed without starting a sandbox. Browsing history works even when no workspace is running; resuming a conversation is the only step that needs a sandbox to boot.
Opening history
Press the History button beside the Agent launcher in the bottom bar. A menu appears above the bar with your recent conversations for the current scope. Each row shows the auto-generated title, the relative date, and the message count.
The list is scoped to match the active conversation. When the panel has a project pinned, history shows conversations for that project. When the panel is in platform scope, it shows platform conversations.
Resuming a conversation
Click any row to resume it. If no sandbox is running, the panel boots one and attaches it to the selected session as soon as it is ready. The panel header updates to show the conversation title.
If the sandbox cannot start, the panel reports that history is unavailable for that session. You can still browse other rows.
Interview sessions
Conversations from the onboarding interview appear in the list with an Interview label. Clicking one navigates to the onboarding page for that project rather than loading the transcript in the chat panel. The interview runtime is separate from the assistant, and the transcript lives there.
FAQ
Where are transcripts stored?
The backend stores transcripts on disk alongside sandbox state. They persist after the sandbox stops, so browsing history costs nothing and works when the workspace is cold.
Why does the history button only appear when a session is active?
The history button beside the launcher is rendered only when a session handle exists, which requires at least one conversation to have started. On a fresh login with no prior conversations, the button is not shown. Open the panel and start a conversation; the button appears beside the launcher on the next page load.