C:/Program Files/Git/resume only shows 1 of 4 sessions from same project/day

Bug: /resume command shows incomplete session list

Environment

• Claude Code version: 2.1.104
• OS: Windows 11 Home 10.0.26200
• Shell: Git Bash

Steps to reproduce

1. Work on a project across multiple sessions in the same day (4 sessions in my case)
2. All sessions are in the same working directory and on the same git branch (master)
3. Run /resume inside Claude Code

Expected behavior

All 4 sessions should appear in the /resume list.

Actual behavior

Only 1 session appears: the one originally created on an older Claude Code version (2.1.78). The other 3 sessions created on version 2.1.104 do not appear.

Investigation

I inspected the JSONL session files in ~/.claude/projects/<project>/. All 4 sessions exist on disk with valid data:

| Session | Modified | Size | custom-title | Version | Shows in /resume? |
|---------|----------|------|-------------|---------|-------------------|
| 02c889f9 | 10:52 | 3.9MB | chatwoot-z-api-whatsapp-bridge | 2.1.78 | Yes |
| 1ec85e28 | 15:29 | 1.9MB | asaas-e2e-integration-test | 2.1.104 | No |
| ee5260c8 | 13:11 | 0.3MB | (none) | 2.1.104 | No |
| 84e1a785 | 16:27 | 0.1MB | (none — current session) | 2.1.104 | — |

Key difference: the only session that appears was originally created on version 2.1.78 (directory created Mar 19, JSONL updated today). The sessions created on 2.1.104 are invisible to /resume.

All sessions have:

• Same cwd (project directory)
• Same entrypoint: "cli"
• Valid JSONL with user and assistant message entries
• Two of the three missing sessions have custom-title entries

The sessions created on 2.1.104 also have a permission-mode entry at the top of the JSONL (the 2.1.78 session does not). This may be related to the filtering logic.

Impact

Users lose access to recent conversation history and cannot resume work from previous sessions, forcing them to rebuild context manually each time.