Session persistence
Sessions and their message history persist locally across restarts.
Every session's message history is stored locally — in a SQLite database (via sql.js) inside Electron's per-user application-data directory — and persists across app restarts. There's no remote backend or account system involved.
Multiple sessions per project
A workspace can hold multiple sessions at once, switchable from a sidebar. Session titles are generated automatically from the conversation rather than requiring you to name them up front.
Handoff between agents
Within a session, AgentDock can build a mechanical summary of the requests made, files touched, and open issues so far, and let you continue the same line of work in a different agent. This is session-scoped: the handoff carries context forward without requiring you to re-explain it, and works across any of the three supported agents. See Agents overview for how the agents differ.
Related
- Workspace overview
- Compare Mode — running the same prompt against multiple agents at once, rather than handing off sequentially.