/resume returns 'No conversations found' despite valid sessions-index.json

Description

The /resume command consistently returns "No conversations found to resume" even though:

• Session files exist (188 .jsonl files in ~/.claude/projects/-home-user-c3d/)
• sessions-index.json exists with valid entries
• history.jsonl tracks sessions with valid session IDs

Environment

• Claude Code version: 2.1.31
• Installation method: Native installer (~/.local/bin/claude -> ~/.local/share/claude/versions/2.1.31)
• OS: Linux 6.6.111+
• Platform: linux

Steps to Reproduce

1. Have existing conversation sessions in ~/.claude/projects/<project>/
2. Run /resume command
3. Observe "No conversations found to resume" message

Attempted Fixes (none worked)

1. Deleted sessions-index.json - Index was not regenerated by Claude Code
2. Cleared statsig cache (~/.claude/statsig/*) - No effect
3. Manually rebuilt sessions-index.json from session files with valid schema - Still no conversations found

Diagnostic Information

sessions-index.json structure (valid)

{
  "version": 1,
  "entries": [
    {
      "sessionId": "uuid",
      "fullPath": "/home/user/.claude/projects/-home-user-c3d/uuid.jsonl",
      "fileMtime": 1234567890,
      "firstPrompt": "...",
      "summary": "...",
      "messageCount": 50,
      "created": "2026-01-14T23:27:22.351Z",
      "modified": "2026-01-15T02:00:19.358Z",
      "gitBranch": "master",
      "projectPath": "/home/user/c3d",
      "isSidechain": false
    }
  ]
}

Session files exist

$ ls ~/.claude/projects/-home-user-c3d/*.jsonl | wc -l
188

history.jsonl tracks sessions

{"display":"/resume ","timestamp":1770231653390,"project":"/home/user/c3d","sessionId":"95be4212-b297-42f9-8281-fa46467eabb6"}

Debug logs show no relevant errors

• No errors related to session loading or index reading
• Only non-fatal lock acquisition messages

Expected Behavior

/resume should display a list of previous sessions from the index.

Actual Behavior

/resume returns "No conversations found to resume" immediately without showing any sessions.

Related Issues

• #18311 - Similar report of /resume not finding sessions
• #19995 - Same symptom reported

Notes

• Direct resume by session ID (claude --resume <session-id>) was suggested as workaround but not tested
• Issue persists across multiple fresh Claude Code sessions