--resume <session-id> returns 'No conversation found' despite valid .jsonl file on disk

Resolved 💬 1 comment Opened May 27, 2026 by cameron-hebert-shortok Closed May 27, 2026

Reproduction

cd /path/to/project  # correct project directory where session was created
claude --resume 35814092-99b2-4a66-99e1-1dc2cbd7fc10
# Output: "No conversation found with session ID: 35814092-99b2-4a66-99e1-1dc2cbd7fc10"

Evidence the session exists

~/.claude/projects/<project-dir>/35814092-99b2-4a66-99e1-1dc2cbd7fc10.jsonl
  - 95 lines, 15KB, last modified today
  - First line contains {"type":"pr-link","sessionId":"35814092-99b2-4a66-99e1-1dc2cbd7fc10",...}
  - Has companion directory with 14 subagent files and tool-results/

The file is present, non-empty, and contains the exact session ID being requested.

Environment

  • Claude Code 2.1.143
  • macOS Darwin 25.4.0 (Apple Silicon)
  • Running from the correct project directory (same cwd where session was created)

Expected

Session resumes normally.

Actual

"No conversation found with session ID: 35814092-99b2-4a66-99e1-1dc2cbd7fc10"

Additional context

  • Session was renamed multiple times via /rename during its lifetime — unclear if that's related to the lookup failure
  • The session .jsonl file starts with a pr-link type entry rather than a conversation message — this may confuse the lookup parser expecting a specific first-line format
  • claude -c (continue most recent) works as a workaround, but --resume <id> with the exact UUID does not
  • The --resume interactive picker also sometimes fails to list sessions that exist on disk

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗