Sessions
A session keeps one line of work together: messages, selected agent and model, tool activity, questions, permissions, progress, and usage.
Continue the current session
Continue when the next request depends on decisions, files, or results already discussed. The existing transcript helps the agent interpret the follow-up.
Start a new session for unrelated work or when you want a clean conversation context. Separating work makes results easier to review and find later.
Sessions in each interface
| Interface | How sessions are organized |
|---|---|
| VS Code Chat | One focused session in the current checkout, with local History. |
| Agent Manager | Sessions and terminal tabs grouped under Git worktrees. |
| Reasoning Board | A prepared session created from selected requirement context. |
| Reasoning CLI | Interactive or headless sessions started and continued from the terminal. |
The VS Code extension and the CLI share the session history stored on your computer, so you can resume in one a session started in the other.
Long or portable sessions
Use /compact to summarize an active conversation before continuing with less history. Use /export to save the transcript as Markdown.
In VS Code, History lists local sessions. In the terminal, see Interactive Terminal.