/resume command reports 'No conversations found' despite conversations existing on disk

Bug Description

The /resume command consistently reports "No conversations found to resume" even immediately after exiting a conversation, despite conversation files being properly saved to disk.

Environment

• OS: Linux (Ubuntu on Azure VM)
• Claude Code Version: Latest (installed via npm)
• Shell: zsh

Steps to Reproduce

1. Start a Claude Code session in a project directory
2. Have a conversation (ask a question, get a response)
3. Exit the session (Ctrl+C or /exit)
4. Immediately run claude again in the same directory
5. Run /resume
6. Observe: "No conversations found to resume"

Expected Behavior

/resume should list recent conversations from the current project and allow selecting one to resume.

Actual Behavior

/resume returns "No conversations found to resume"

Evidence

Conversations ARE being saved correctly:

$ ls -lt ~/.claude/projects/-home-chrissun-elser/*.jsonl | head -5
-rw------- 1 user user   34603 Jan 22 06:16 d8a06ba6-d7ea-453e-997e-e67241f23d0f.jsonl
-rw------- 1 user user   60702 Jan 22 06:15 ab6b324d-b413-4460-8915-175414b3de69.jsonl
-rw------- 1 user user   12985 Jan 22 06:05 c23b2ca2-507a-41df-a0be-6e0b4eef965d.jsonl
...

The ~/.claude/history.jsonl file also contains proper entries:

{"display":"example prompt","timestamp":1769062085766,"project":"/home/chrissun/elser","sessionId":"ab6b324d-b413-4460-8915-175414b3de69"}

Workaround

Manually specifying the session ID works:

claude --resume ab6b324d-b413-4460-8915-175414b3de69

Additional Context

• This issue is reproducible and persistent (not a one-time occurrence)
• The project directory is /home/chrissun/elser
• Multiple conversation files exist spanning several days
• The issue occurs regardless of conversation length or content