claude --continue and --resume show blank session despite valid session data
Status Fixed / completed
Reported on v2.1.96
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 4 comments · opened Apr 8, 2026 · closed Apr 8, 2026
Description
claude --continue and claude --resume <session-id> open a blank session instead of displaying the conversation history, even though the session files exist and contain valid data.
Steps to Reproduce
- Have existing sessions in
~/.claude/projects/<project>/ - Run
claude --continuefrom the project directory - A blank session appears instead of the most recent conversation
- Run
claude --resume <session-id>with a specific session ID - Same result — blank session
Expected Behavior
The conversation history should be displayed and the session should resume where it left off.
Observed Behavior
A blank/new session appears with no conversation history, despite the session .jsonl files being present and containing valid JSONL data (e.g. 227 lines, ~810KB).
Environment
- Claude Code version: 2.1.96
- Platform: Linux (CachyOS, kernel 6.19.9-2-cachyos)
- Shell: bash
- Session files are present in
~/.claude/projects/with correct permissions (-rw-------) and valid content
4 Comments
Workaround: Start a new session in the project directory and ask Claude to read the latest conversation from
~/.claude/projects/<project>/and update a project CLAUDE.md from it, so the next session has context. Not ideal but functional.Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Indeed duplicate
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.