Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallIf claude --continue does not reopen the conversation you need, first return to the project directory where you used Claude Code. The flag loads the most recent conversation in the current directory; to target a particular conversation, use claude --resume <session-id> or try the interactive chooser with claude --resume.
Why --continue may not find the session
Anthropic documents --continue (also -c) as loading the most recent conversation in the current directory. It is not documented as a search across every project. If you start Claude Code from a different directory, it may therefore continue a different conversation or fail to select the one you want. See the Claude Code CLI reference.
As an Amazon Associate I earn from qualifying purchases.
Try these recovery steps
-
Return to the original project directory
In your terminal, change to the repository or project directory where the session took place, then run
claude --continue. This is the first check because the command is scoped to the current directory.Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Resume the exact session by ID
If you have the session ID in notes, shell history, logs, or an SDK output capture, run:
#1 Best Overall
claude --resume <session-id>The short form is
claude -r <session-id>. The CLI reference also supports adding a follow-up prompt after the ID. Use the ID for the conversation you intend to reopen. -
Choose from available sessions
If you do not know the ID, run
claude --resumewithout an ID and use the interactive session chooser if it appears. The documentation describes interactive selection, but does not guarantee that every past session will be listed. -
For SDK workflows, capture the session ID next time
Anthropic’s SDK documentation shows JSON output being parsed for
session_idand that value then supplied toclaude -p --resume. For example, the documented pattern uses--output-format jsonandjqto save the ID. Adapt the command to your shell and workflow; this helps only if you actually captured the ID.Free tools Windows power users keep installed
One-click scans. No signup required.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
If resuming still fails
Collect details that can help distinguish a version or installation issue from unavailable session data. Anthropic documents claude --version, claude doctor, and the --verbose flag for detailed turn-by-turn output. To reproduce the problem with verbose output, use the same project context and command that failed. The setup guide describes claude doctor as an installation-type and version check.
Rank #3
claude update is the documented manual update command. Updating may be useful when investigating version-related behavior, but Anthropic’s reviewed documentation does not describe it as a way to restore missing or damaged session data.
- Keep the session ID, if you have it.
- Save the exact command, current project directory, installed version, and error output.
- Check the installed CLI’s current help and contact Anthropic support for version-specific guidance.
The official documentation reviewed does not establish a universal transcript-file path or a supported procedure for moving, renaming, or manually editing session data. Avoid making those changes based on an assumed path.
Rank #4
What Anthropic says about local session retention
Anthropic’s data-usage documentation says local Claude Code clients may store sessions locally for up to 30 days so users can resume them. That is a stated retention window, not a guarantee that a particular session is still present or can be recovered.
Quick Recap
Which resume method should you use?
| Method | Use it when | Limitation |
|---|---|---|
claude --continue |
The conversation you want is the most recent one in the current directory. | It selects the most recent conversation in that directory, not a documented cross-project search. |
claude --resume <session-id> |
You have the ID for the exact conversation. | Requires the correct ID; it cannot guarantee recovery if the session data is unavailable. |
claude --resume |
You do not have an ID and want to select from sessions offered interactively. | The documentation does not promise that a specific historical conversation will appear. |
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.




