Find an Old Claude Code Conversation Fast

A Claude Code session you can't find is almost never gone — it is sitting in a file on your disk. Claude Code saves every session to ~/.claude/projects and does not delete them on its own, so the real problem is retrieval, not loss. Below is exactly where to look, and how to search every session by keyword in seconds.

The thing that makes an old session feel lost is how retrieval works. Claude Code groups sessions by the project directory you ran them in, and claude --resume only ever lists sessions for the directory you're currently in — even if you know a session's exact ID. Its built-in tools are also made for resuming a session, not for searching what was said inside your past conversations. So the moment a session is in a different project, or you're hunting for it by something that happened inside it rather than by recognising the session itself, the built-in tools stop helping — even though the file is right there.

Method 1: Look in the resume picker

If you can recognise the session in the picker, this is the quickest route:

1. cd into the project directory the session belongs to — both claude --resume and claude --continue only see sessions for the directory you're in.
2. Run claude --resume, then filter the list with a search term, or scroll to the session.
3. Pick it to reopen. (claude --continue jumps straight to the most recent session in that directory.)

Works well for: a session you can spot from its entry in the list.

Breaks down when: you're trying to find a session by something that was said inside it — the picker helps you resume a session, not search its contents.

Method 2: Browse the session files directly

Every session lives under ~/.claude/projects, in a subfolder named after the project directory. You can open that folder and look around:

1. Open ~/.claude/projects (it is a hidden folder — enable "show hidden files" if needed).
2. Each subfolder is one project; the folder name maps to the directory you ran Claude Code in.
3. Inside are .jsonl files, one per session, named by session identifier.

Browsing by folder helps when you remember the project but not the exact session — you can narrow to the right project, then open files to find the one you want.

Works well for: narrowing down when you remember the project but not the session.

Breaks down when: a project has many sessions, or you don't know the project at all — file names are identifiers, not descriptions.

Method 3: Search the files by content with ripgrep

When you remember what was in the conversation but not where it was, search by content instead of by folder:

rg -i "a phrase you remember" ~/.claude/projects

That returns the session files containing your phrase, and each file's parent folder tells you which project it belonged to. From there you can cd into that project and resume it.

Works well for: a distinctive phrase — a function name, an error message, a decision.

Breaks down when: you are reading raw JSONL, so matches are mixed in with tool calls and file contents, and you still have to open the file to read the exchange around the match.

Method 4: Search every session with LLMnesia

Methods 1–3 all ask you to either remember the project or sift through raw files. LLMnesia removes both steps: it indexes your Claude Code sessions locally and makes every one of them searchable by keyword — across every project, from one box.

Point it at your ~/.claude/projects folder once, or install the optional background helper so new sessions are indexed automatically as you create them. Type a phrase you remember and jump straight to the session, then reopen it in the Claude Desktop app or copy a command that resumes it in the right folder. The same index covers your ChatGPT, Claude, and Gemini history too, and it all stays on your device — it reads the sessions already on your disk rather than storing a second copy in the cloud.

Stop losing sessions in the first place

Keep projects in stable directories. Moving or renaming a project directory splits its history across two folders, making old sessions harder to place later.

Note the project for work you'll return to. If a session solved something you know you'll need again, jot the project path somewhere — a fifteen-second note saves a long hunt later.

Index your sessions for search. The durable fix is to make every session findable by what it contains, not by which folder it lives in. Once your history is searchable by keyword, "find that old Claude Code conversation" becomes a two-second search instead of an archaeology project.