[BUG] No conversation found with session ID
Status Fixed / completed
Maintainer reply ✓ Yes — wolffiex
Activity 8 comments · opened Jun 16, 2025 · closed Jul 18, 2025
💡 Likely answer: A maintainer (wolffiex, collaborator)
responded on this thread — see the highlighted reply below.
Environment
- Platform (select one):
- [x] Anthropic API
- [ ] AWS Bedrock
- [ ] Google Vertex AI
- [ ] Other: <!-- specify -->
- Claude CLI version: 1.0.19
- Operating System: Ubuntu 22.04.5 LTS
- Terminal: tmux (ssh'd in with iTerm 2)
Bug Description
On this machine, claude --resume <session ID> doesn't work; it just always says: No conversation found with session ID <session ID>. I've ensured that I'm running in a consistent directory, and running simply claude --resume does list the session (and resuming interactively works)
Steps to Reproduce
- Run eg
echo <prompt> | claude -p --verbose --output-format=stream-json --allowedTools '...' - Take note of the session ID in the response messages
- Run simply
claude --resume <session ID>(or send another prompt with the same--resumeparam)
Expected Behavior
The prompt should be handled correctly, resuming the previous session
Actual Behavior
The error message described above is printed instead.
Additional Context
The same repro works fine locally on my Mac. I'm not sure how sessions are stored or looked up, but presumably there's something about the machine I'm ssh'd into that causes this issue? Happy to help track this down!
8 Comments
Can you
ls ~/.claude/projectsOn the machine that's having issues:
On my Mac, I have:
Are there files in these directories? You are aware that sessions are tied to the directory where claude starts, right?
Yes, and yes (I mentioned in the bug description that I ensured I was in a consistent directory).
Ok interesting thanks. Is 77901b87-d4e1-489a-944a-0605a7ef2386.jsonl a
valid jsonl file? You can check with jq
On Wed, Jun 18, 2025 at 9:15 AM Daniel Leong @.***>
wrote:
Appears to be. Ran jq and trimmed the content a bit:
jq without the param throws a (presumably, expected) error:
It seems to be working for me now. I'll go ahead and close, and open a new issue if I run into other problems. Thank you!
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.