Pick up agent conversations after a restart

What comes back by itself

Workspaces, folders, pane layouts, tab names and appearance settings. By default nothing is running: each terminal shows Ready to start with a shell selector, and the workspace notice offers Start all shells. Previous processes are never resumed and commands are never replayed.

What you can resume

If Claude Code or Codex was running in a terminal when SplitNest closed, that terminal says so and offers Resume Claude Code (or Codex) next to Start PowerShell only. The notice offers Resume agents (N) for the whole workspace. The text above the button states exactly what will run, and nothing runs until you click.

What it types

A new PowerShell starts in the folder the agent ran in, and claude --resume <id> or codex resume <id> is typed at the prompt, visibly. Two Claude Code agents in the same folder each resume their own conversation. If SplitNest cannot be sure which conversation was meant, it opens the agent's own list of earlier conversations instead of guessing.

What is stored

The agent, the conversation id, the folder, and optionally the conversation title shown above the button. Never conversation text. Titles can contain words from your prompt, so you can turn them off in Settings → Workspaces, which also removes the saved ones. Resume works through the agents' own session records, so no hooks or agent settings are installed.

Prefer it automatic?

Settings → Workspaces has Resume agents automatically when the app opens, off by default. It resumes them without a click, each workspace the first time it is shown.

Limits

In WSL tabs SplitNest cannot tell which conversation ran, so Resume opens the agent's own list. Codex's /new is not followed. If an agent ran in a folder outside the workspace folder, Resume is refused and the terminal offers a plain shell. The agents' session files are undocumented, so a future agent update may make Resume fall back to the agent's list.