SymvibeDocs
  1. Docs
  2. Agents and consoles
  3. Resume and quitting

Resume and quitting

Symvibe saves the board, not the processes. Consoles always start fresh when a board reopens, and the ones whose CLI supports it offer to pick their conversation back up.

Updated October 22, 20262 min read

On this page

When you quit#

  • With consoles running, Symvibe asks first: Quit Symvibe? with how many sessions will end. Closing the window quits the app too, with the same question.
  • Each console gets a quit signal and a moment to exit, then is stopped. No agent keeps running after the app is gone.
  • If Symvibe crashes or is force-quit, a small watchdog stops the consoles it started. A program an agent deliberately detached from its terminal, such as a background server, is left alone.
  • Closing a console, a workspace or a repo stops the consoles in it the same way.

When you reopen#

  • Each console starts its CLI again in the same place, with a note that it was restored. Its old scrollback is gone.
  • If SettingsGeneralResume agent chats is on, which it is by default, and the CLI supports it, the console shows Resume last conversation? Click it to pick the conversation back up; typing instead starts fresh.
  • When several consoles have something to resume, a banner offers Resume all conversations? with Yes and No.
Consoles restored on reopen, each offering to resume its conversation.

Which conversation is offered#

CLIWhat is offeredHow it resumes
Claude CodeThat console's own conversation, if its transcript is still on diskclaude --resume with the session id
CodexThat console's own sessioncodex resume with the session id
GeminiThe most recent conversation in the folder, offered on the console that chatted lastgemini --resume latest
OpenCodeThe most recent conversation in the folder, offered on the console that chatted lastopencode --continue
Grok, Shell and other agentsNothing; they start freshNone

If a Claude Code or Codex resume exits within eight seconds, the offer comes back. A Gemini or OpenCode resume with nothing to resume starts fresh.

When the Mac sleeps#

Consoles keep their processes through sleep. After more than 90 seconds asleep, each running console on the workspace you have open prints a dim note that network sessions may have dropped, except one showing a full-screen program. The subscription check waits until the Mac is fully awake.

Keep going#

Repos and workspacesHow boards are saved and archived. Agent consolesRestart, close and the status pill. SettingsResume agent chats and the rest of General.

Something on this page does not match what you see in the app? Write to hello@symvibe.com or tell us in the Discord, and we will fix it.