Repository navigation
/resume missing sessions: sessions-index.json out of sync with actual session files #25552
Closed as not planned
Description
Bug
/resume doesn't show all past conversations. Sessions exist on disk as .jsonl files but are missing from sessions-index.json, making them invisible to the /resume picker.
Repro
- Use Claude Code extensively over time (~160+ sessions)
- Run
/resume— only a subset of sessions appear - Compare actual
.jsonlfiles on disk vs entries insessions-index.json
Evidence
In my case:
- 162
.jsonlsession files on disk in the project directory - 98 entries in
sessions-index.json - 64 sessions (~40%) are orphaned — fully intact on disk but invisible to
/resume
The missing sessions can still be resumed by passing the UUID directly (claude --resume <uuid>), confirming the data is fine — it's just the index that's stale.
Expected behavior
All sessions should appear in /resume. The index should stay in sync with session files on disk, or /resume should fall back to scanning the directory.
Environment
- macOS (Darwin 23.6.0)
- Claude Code v2.1.38
Reacted by Csaba Endre Simon and Lee Reinhardt
Activity
github-actions commentedon Feb 13, 2026
Found 3 possible duplicate issues:
claude --resumeto show stale/missing sessions #25032This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
scapeshift-ojones commentedon Feb 16, 2026
This issue is tracked in the consolidated report at #26123, which identifies 3 distinct root causes (index writes stopped Feb 4, picker hardcoded to 10-session batch, Windows worktree case-sensitivity) with source-level analysis and a one-line fix. Please add your thumbs-up there to help it reach the oncall triage threshold.
scapeshift-ojones commentedon Feb 16, 2026
Your 👍 on the consolidated issue matters. Based on how this repo's automated triage works, issues need 50+ combined reactions and comments to trigger the oncall label — the only way a human at Anthropic actually reviews it. Right now the engagement is split across 12+ duplicate issues and none will ever hit that threshold alone.
The consolidated issue with full root cause analysis (3 bugs identified, one-line fix included) is here: #26123
Please go add your 👍 there. That's the single most useful thing you can do to get this fixed.
scapeshift-ojones commentedon Feb 17, 2026
We're at 22 👍 on the consolidated issue — more than halfway to the 50 needed to get a human at Anthropic to look at this. Every thumbs-up on a duplicate issue is a thumbs-up that doesn't count. The automated triage bot only checks individual issues, not the cluster.
Please take 5 seconds to 👍 here: #26123
The root causes are fully identified, a one-line fix exists, and community repair scripts are available. The only thing missing is enough engagement on a single issue to cross the oncall threshold. We can get this fixed if we stop splitting our votes across 12 separate reports.
github-actions commentedon Mar 17, 2026
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
github-actions commentedon Mar 26, 2026
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.