Resume Sessions After Restart
When you close DevWorkspace Pro, it keeps a record of sessions that are not finished. When you start the app again, you can continue:
- AI sessions that you started with New AI session or Send to AI. See AI Sessions.
- The Terminal tab of each project, with each of its terminals.
Both are on by default. Open Preferences → General:
| Setting | What it does |
|---|---|
| Resume AI Sessions After Restart | Keeps unfinished AI sessions. When you turn it off, DevWorkspace Pro deletes the saved sessions. |
| Keep Unfinished AI Sessions (days) | Deletes an unfinished AI session after this number of days. Default 90, Min 1, Max 365. |
| Restore Terminal Tabs After Restart | Keeps the text and folder of each Terminal tab. When you turn it off, DevWorkspace Pro deletes the saved text. |
AI Sessions
What DevWorkspace Pro saves
DevWorkspace Pro saves the tool, the session ID of the tool, the project folder, the arguments from AI CLI Tool Arguments, the title of the task and the start time.
DevWorkspace Pro does not save your prompt. The prompt stays in the session history of the AI tool.
The record is deleted when:
- The AI tool stops (for example, you type
/exit). - You click Close on the terminal window.
- You discard the session.
If you quit DevWorkspace Pro while the AI tool is open, the record stays. On macOS, when you close the main window, the AI tool and the terminals stop and the records stay. Open the window again to resume.
Resume a session
After a restart, the status bar shows a button with a history icon, for example 2 to resume. The project page also shows the number of unfinished sessions next to New AI session. On the dashboard, the card of a project with unfinished sessions shows a resume button with the number of sessions.
- Click the button. A list shows the sessions, grouped by project. Each session shows the tool, the start time and the days before it expires. Hover over the title to see the folder and the arguments.
- Click Resume next to a session. To resume more than one session, click Resume all or the Resume button of a project.
The AI tool opens in a terminal window, in the same folder, with the same conversation and the same arguments. DevWorkspace Pro never starts a session by itself.
To remove sessions, click Discard or Discard all. The notification has an Undo button.
Arguments
A resumed session uses the same arguments as the first session, for example --dangerously-skip-permissions or --yolo. Check the arguments before you click Resume.
How each tool resumes
| Tool | How DevWorkspace Pro gets the session ID | Resume command |
|---|---|---|
claude | DevWorkspace Pro sets the ID when it starts the session (--session-id). | claude --resume <id> |
codex | DevWorkspace Pro finds the new session file in ~/.codex/sessions (or $CODEX_HOME/sessions) for the same folder. | codex resume <id> |
opencode | DevWorkspace Pro finds the new session with opencode session list for the same folder. | opencode --session <id> |
For codex and opencode, DevWorkspace Pro looks for the session ID shortly after the start. If it does not find one session that matches, it does not save the session.
DevWorkspace Pro saves only the sessions that it can identify. For example, claude --continue or claude --resume with no session ID is not saved for resume.
When a session is not shown
DevWorkspace Pro shows a session only when all of these are true:
- The session started (or was last resumed) less than Keep Unfinished AI Sessions (days) ago.
- The project folder still exists.
- The AI tool still has the session. For
claude, the session file must be in~/.claude/projects(or$CLAUDE_CONFIG_DIR/projects).
DevWorkspace Pro deletes the records that fail these checks.
Claude Code cleanup
Claude Code deletes its own session files after cleanupPeriodDays (default 30) in ~/.claude/settings.json. To resume older Claude sessions, set cleanupPeriodDays to the same value as Keep Unfinished AI Sessions (days) or higher.
WSL
On Windows with a WSL distribution, only claude sessions can be resumed. DevWorkspace Pro cannot find the session IDs of codex and opencode inside WSL.
Terminal Tab
DevWorkspace Pro keeps the screen text and the working folder of each terminal in the Terminal tab of each project. It restores each terminal.
When you open the Terminal tab after a restart:
- The terminal shows its recent saved output.
- A line shows the time of the save:
── Restored from … Commands above are not running. ── - A new shell starts below that line, in the last folder that you used.
DevWorkspace Pro never runs the old commands again.
DevWorkspace Pro saves recent output automatically and when you close the app. Saved output that is older than 60 days is not restored.
Working folder
On macOS and Linux, DevWorkspace Pro reads the working folder of the shell. On Windows and in WSL, the new shell starts in the project folder.
If the App Stops Unexpectedly
If DevWorkspace Pro crashes, or the operating system stops it:
- AI sessions: You can resume them. DevWorkspace Pro saves each record when the session starts. If the app stops a few seconds after the start, the AI tool can have no saved session yet. DevWorkspace Pro then deletes the record at the next start.
- Terminal tab: DevWorkspace Pro restores the last save. The output from the moments before the stop can be missing.
- Saved data: DevWorkspace Pro writes each file to a temporary file first, and then replaces the old file. If the app stops during a write, the old file stays complete.
Privacy
All the saved data stays on your computer, in the DevWorkspace Pro data folder (session-resume.json and the terminal-snapshots folder). The saved terminal text can contain secrets that a command printed, for example tokens or passwords. To keep no terminal text on disk, turn off Restore Terminal Tabs After Restart.