Last updated 6 October 2026
Claude Code resume: picking a session back up after a restart
Every Claude Code session is stored on disk as a conversation, keyed to the folder it ran in. Closing the terminal does not delete it. That means a reboot, a crash or an accidental Cmd+Q costs you nothing, as long as you resume instead of starting over.
The two flags
claude --continue reopens the most recent conversation for the current folder. claude --resume shows a picker of past conversations for that folder and lets you choose one.
In practice --continue is what you want nine times out of ten. Use --resume when you had several unrelated sessions in the same folder and need a specific one.
What comes back
The full message history, the files the agent read, the decisions it made and the plan it was following. What does not come back: running processes. A dev server the agent started is gone after a reboot and needs starting again.
Making it automatic
If you run several sessions, remembering which folder had which conversation is the hard part. adhdTerminal stores the session id with each tile, and on launch opens every tile with the matching conversation. The wall after a restart looks exactly like the wall before it.
Read next
- How to run five Claude Code sessions at once without losing oneParallel agent work fails at the attention layer, not the compute layer. A practical setup for keeping every running session visible.
- The restart tax: why tabs are the wrong unit for agent workA tab you cannot see is a job you will restart. The hidden cost of hiding running work behind a title bar.
- Naming agent sessions: why the agent should name itselfFolder names describe projects, not jobs. Letting the session write its own title keeps the wall honest.
- Full Disk Access and Claude Code on macOS: what the permission doesWhy a terminal app asks for Full Disk Access, what Operation not permitted means, and how to grant it once.