Sessions that survive ⌘Q

Quit, crash or update Seedmux mid-task and your agents keep working.

Quit whenever you like

Every pane runs in a session that belongs to your Mac, not to the Seedmux window. So when you:

• press ⌘Q,
• install an update,
• or Seedmux crashes,

…your agents don't notice. Open Seedmux again and every space, tab, split and line of scrollback is back where it was — plus whatever the agents finished while you were away.

Closing the window with the red button doesn't even quit: Seedmux keeps running, the Agents panel and the notch keep working, and the Dock icon, the global hotkey or the island bring the window back.

The only thing that really ends a session is closing its pane with ⌘W.

Apps you open from a pane

Opening an app from the terminal — say open -a LibreOffice — and then quitting or force-quitting it won't take your sessions down with it.

After a restart

Restarting your Mac does end the processes in your panes. Seedmux still remembers which agent and which conversation each pane had. The first time you click such a pane, it picks the conversation back up for you — Claude Code, Codex, Grok, OpenCode, Kimi Code, Antigravity and others resume where they left off. If the folder no longer exists, Seedmux types the command at the prompt without running it, so you can check first.

Even if the background process holding your sessions is ended unexpectedly, your tabs stay: each pane starts a fresh shell in the folder it was in, and running agents pick up their conversation again.

Recover missing tabs

Settings › Terminal › Recover Missing Tabs lists sessions that are still running but have no tab — after a layout mishap, for example — and brings them back without starting anything new.

Your layout, saved

Spaces, tabs, splits and their sizes, which pane had focus and each pane's folder are saved as you go and restored on every launch.