claude --resume <session-id> always returns 'No conversation found' even though session files exist

Bug Description

claude --resume <session-id> consistently returns "No conversation found with session ID: \<id\>" even though the corresponding .jsonl session files exist on disk.

Environment

• Claude Code version: 2.1.74
• OS: macOS Darwin 24.6.0
• Node: (via npm global install)

Steps to Reproduce

1. Start a Claude Code session and have a conversation
2. Exit the session
3. Check that the session file exists:

``
ls ~/.claude/projects/<project-dir>/<session-id>.jsonl
``

1. Try to resume:

``
claude --resume <session-id>
``

1. Result: No conversation found with session ID: <session-id>

Session File Structure

The .jsonl files exist and contain valid data. Each message entry has both a uuid (matching the filename) and a sessionId field. For example:

{"parentUuid":null,"type":"user","uuid":"b11d010a-...","sessionId":"b11d010a-...","gitBranch":"feature/xyz"}

The last entry in the file is a custom-title record:

{"type":"custom-title","customTitle":"ws_sharing","sessionId":"b11d010a-..."}

Also Tried

• /resume inside an active session → "No conversations found to resume"
• claude --continue → starts a new session instead of resuming
• Multiple different session IDs → all return the same error

Expected Behavior

claude --resume <session-id> should successfully resume the conversation from the stored .jsonl file.