Resume old sessions

Yes please! Being able to save/resume/fork conversations would be delightful.

Absolutely! Please add this.

Coming here after accidently closing _once again_ the terminal in which Claude Code was running, losing all context...

just for using CC I installed gnome-terminal which has a confirm dialog on close when there is an active process running, trust me you won't regret it...

Have you tried the ideas in https://github.com/ChristopherA/Claude-Code-CLI-Toolkit ? I keep a separate context for every branch of my repo. Allows me to /exit and restart, or go do another feature for a while and return.

Ironically, Claude code just hallucinated me this command. Sadly it didn't work.

> how do I park and resume a session?

⏺ Fetch(https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview)…
  ⎿  Received 1.8MB (200 OK)

⏺ To park and resume a Claude Code session, you can use:

  1. To park (save) a session:
  /park [optional session name]
  1. This saves your current conversation state for later access.
  2. To resume a session:
  claude code --resume [session name or ID]
  2. This loads a previously parked session.

  If you don't specify a session name when parking, Claude will generate a unique ID that you can reference later when resuming.

> /park viewer
  ⎿  Local command /park viewer completely ran.

     Parked session id: viewer

· Accomplishing… (0s · ⚒ 0 tokens · esc to interrupt)

This is shipped! https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md#0293

Thanks. It would still be useful if we could write these /compact contexts to a file.

What is the difference between --resume and --continue. What is the todo list that this changelog refers to?

Understood, we have a transcript export feature on our backlog. Resume is only available in interactive mode. It shows a picker of previous conversations. Continue continues the last conversation.

The Todo List is unrelated, but it helps Claude keep track of where it is in larger tasks. It will trigger automatically or you can explicitly ask claude to use its Todo Tool

As for the --restore feature - this is great!
I do have a few more suggestions:

1. Can we have a custom number of "restored" sessions? One should be able to go a week back for a sepcific task.
2. It would be really nice to be able to just print the available sessions to restore
3. It could also be really useful to set custom session names / aliases - so it would be easier to identify the session you'd like to restore instead of guessing.

@talf I think you mean --resume, not --restore.

Heavy +1 on ability to set custom session names. The --resume feature is great, but finding out which session you want to reattach to is difficult if you have multiple short sessions. It's just a maze of names all of which sounds very similar.

Being able to give a session name, or rename mid session would be a nice qol improvement compared to playing --resume bingo.

Want to add my +1 to the --resume situation being unbearably nondeterministic for me personally. Let's have named sessions.

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.