Repository navigation
[BUG] Not able to --continue sessions with large .jsonl files. Those sessions are also dropped from --resume overview #23072
Description
Preflight Checklist
- I have searched existing issues and this hasn't been reported yet
- This is a single bug report (please file separate reports for different bugs)
- I am using the latest version of Claude Code
What's Wrong?
This might or not be related to this issue: #18311
Some of my prompts are very large. I cannot --continue those sessions. It will tell me:
> claude --continue
No conversation found to continue
What Should Happen?
I should be able to continue my session that physically exist as .jsonl file in .claude/projects
Error Messages/Logs
No conversation found to continueSteps to Reproduce
- Create a new project or worktree
- Run claude and ask it to summarize the following book
- Copy and paste Frankenstein from https://www.gutenberg.org/cache/epub/84/pg84.txt into your terminal
- Wait for claude's response
- Exit claude and run
claude --continue
It will tell you: No conversation found to continue
- Run
claude --resumeand it will show you an empty list. - But if you look up the session id manually and run
claude --resume <UUID>it is able to resume the session
Claude Model
Opus
Is this a regression?
I don't know
Last Working Version
No response
Claude Code Version
2.1.31
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
No response
Activity
github-actions commentedon Feb 4, 2026
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
github-actions commentedon Feb 8, 2026
This issue has been automatically closed as a duplicate of #22462.
If this is incorrect, please re-open this issue or create a new one.
🤖 Generated with Claude Code
github-actions commentedon Feb 15, 2026
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.