Restart Warp.
Keep your context.
Bring your Codex and Claude Code conversations back after a Warp restart. The same sessions, saved quietly on your Mac.
For Apple Silicon and Intel Macs.
No Go, Git, or build tools required.
Let's finish the API refactor.
CodexI have the context. Ready when you are.
Now, the settings screen.
ClaudeWe can pick up from the last change.
Same conversation IDs
Resume the exact captured sessions.
Your working layout
Agent tabs and split panes return together.
Saved on your Mac
Session metadata stays local.
From restart
to resume.
A small background helper remembers your supported agent sessions, so reopening Warp can bring the conversation back with you.
Work as usual
Start Codex or Claude Code in Warp. After installation, the helper starts automatically when you log in.
Your sessions are captured
Every five seconds by default, save session IDs, working folders, and the Warp layout. Keep the snapshot while Warp is closed.
Return to the conversation
When Warp restarts, captured sessions reopen in new windows. Continue from the same conversation when you're ready.
It resumes the conversation ID. Your agent decides how its conversation continues; the helper doesn’t submit a new message for you.
One command.
A little more continuity.
Paste this into Terminal to install the latest release for your Mac. Both CLI names will be available from any directory.
You'll need macOS, Warp Stable, and the Codex or Claude Code CLI already installed.
See the latest releasecurl -fsSL https://warp-restore.ai-infra.org/install.sh | shInstalls warp-restore and warp-agent-session-restore in /usr/local/bin. macOS may ask for your password to put the commands there.
A few commands
worth keeping nearby.
warp-restore and warp-agent-session-restore do the same thing. Use whichever feels natural.
warp-restore statusList saved sessions, their names, and any capture warnings. If there’s no snapshot yet, keep Warp open with an agent running and check again in a few seconds.
Does it resume the same conversation?
Yes. Captured sessions resume using their exact Codex or Claude Code conversation IDs. The tool saves the association between a session, its working folder, and its Warp pane.
It reopens conversations in new Warp windows. It does not automatically send a new prompt or continue an interrupted action.
What does it save, and where?
Session IDs, names, working folders, CLI options, and the Warp layout are kept in owner-only files under ~/.warp-agent-session-restore. Snapshots don’t copy conversation content.
Your agent resumes through its usual CLI. The website doesn’t receive your saved sessions.
What about Warp’s own window restore?
Warp may reopen its previous windows too. This tool opens additional windows for captured agent sessions and preserves supported tabs and split structure.
Exact pane proportions, active-window selection, and custom split-pane labels cannot currently be reapplied.
Which sessions are supported?
Interactive Codex and Claude Code sessions running in Warp on macOS. SSH, tmux multiplexing, and shared background agents aren’t supported.
When Codex supports --no-daemon, installation adds a helper for new Warp zsh tabs. Existing aliases and functions are respected. See the docs for other shells and existing sessions.
What should I know about this early release?
Snapshots are taken every five seconds by default, so a session created and lost between polls cannot be recovered from a snapshot. A recently closed session may be restored during the 20-second shutdown grace period.
On macOS 27, enable Warp data access manually under Warp Restore in Files & Folders. The installer adds ~/Applications/Warp Restore.app for this permission; old entries named warp-agent-session-restore may remain. An update may require enabling access again.
A full Warp restart with real conversations has not yet been validated end to end. Check warp-restore status to confirm what has been captured before relying on a restore.
Can I stop or remove it?
Run warp-restore uninstall to stop the background service and remove managed Claude hooks and the shell block. Saved sessions and installed binaries are preserved.
To keep capturing sessions but require manual restoration, set auto_resume to false in the configuration file.