How to Resume an Old Claude Code Session

To resume a Claude Code session, cd into the project it belongs to, then run claude --resume and pick it from the picker — or claude --continue for the most recent one. Both commands only see sessions for the directory you are standing in, even --resume when you pass a specific session ID, so resuming an old session from a different project starts with knowing (or finding) which directory it lived in. Here is how each option works, and what to do when you can't place it.

The three built-in ways to resume

claude --continue (or -c) — reopens the most recent session in the current directory, no questions asked. This is the "get me back to what I was just doing" option.

claude --resume (or -r) — opens a picker of your saved sessions that you can filter by typing a search term, so you can choose which one to reopen. Use this when the session you want is not the most recent. You can also pass a session ID (claude --resume <id>) to jump straight to a specific one — but like the picker, this only finds sessions belonging to the current directory.

/resume — the same picker, available from inside a running session, so you can switch to another conversation without leaving Claude Code.

All three restore the session's context so Claude picks up with the history intact, rather than starting cold.

The one thing to know about directories

Both claude --continue and claude --resume only operate on the current directory's sessions — and that holds even when you pass a specific session ID to --resume. Try to resume a session from the wrong directory and Claude Code reports it as not found, even though the file is sitting right there under ~/.claude/projects.

So resuming an old session always starts the same way: cd into the project directory it belongs to, then run --continue or --resume there.

Resuming a session you can't place

The built-in tools assume you can recognise the session yourself — by its entry in the picker, or by knowing the directory to run --continue in. Often you can't — you remember what you were doing (a tricky migration, a bug you finally cracked) but not enough to pick it out of a list.

Two ways through it:

• Search the files by content. Every session is a plain file under ~/.claude/projects, named by its session ID. rg -i "something you remember" ~/.claude/projects will point you at the file — its parent folder is the project, and the filename (minus .jsonl) is the ID. cd into that folder and run claude --resume <that-id> to reopen it.
• Let a tool find it and hand you the command. LLMnesia indexes your Claude Code sessions and makes them searchable by keyword across every project. Find the session by a phrase you remember, and it either reopens it in the Claude Desktop app in one click, or copies a ready-to-run terminal command — for the right folder — that resumes that exact session.

Keeping sessions easy to return to

The friction with resuming is almost never the resume command itself — it is finding the right session first. A few habits help:

• Use --continue for same-day work so you never lose the thread of an active task.
• Keep projects in stable directories. Moving or renaming a project directory means its future sessions land in a new folder, splitting your history.
• Index your sessions for search if you regularly return to work from weeks ago. Once every session is searchable by keyword, "which project was that in?" stops being a question you have to answer from memory.

Once you find the session, resuming it is one command — the work is in surfacing the right one, and that is exactly the gap search fills.