[BUG] /resume not listing sessions in v2.1.30 - sessions-index.json not populated
Status Fixed / completed
Reported on v2.1.30
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 14 comments · opened Feb 3, 2026 · closed Aug 19, 2026
Summary
/resume command fails to list any sessions despite valid session files existing. This issue persists in the latest version (2.1.30).
Steps to Reproduce
- Start Claude Code in any directory
- Have a conversation
- Exit the session
- Run
claude --resumeor use/resumecommand - Observe: No sessions are listed
Expected Behavior
Previous sessions should appear in the resume picker for selection.
Actual Behavior
The resume picker shows no available sessions, even though .jsonl session files exist in the project directory.
Environment
- Claude Code version: 2.1.30 (latest as of 2026-02-04)
- Platform: Windows 11
- Installation: winget
Related Issues
This appears to be a continuation of:
- #22205 - Sessions not added to sessions-index.json, invisible to resume
- #16579 - Sessions without summary header don't appear in /resume picker
- #22059 - /resume hangs at Loading conversations...
Filing this separately to confirm the bug persists in v2.1.30 and affects Windows platform.
Workaround
Sessions can be resumed manually if you know the session ID:
claude --resume <session-id>
Session files are located at:
- Windows:
%USERPROFILE%\.claude\projects\<project-hash>\ - Mac/Linux:
~/.claude/projects/<project-hash>/
Request
Please prioritize fixing the session indexing mechanism. The /resume feature is critical for maintaining workflow continuity across sessions.
Showing cached comments. Read the full discussion on GitHub ↗
13 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Fixed for me rolling back to 2.1.29
This is also occurring on v2.1.31.
This is also occurring on 2.1.34 still for me:
<img width="575" height="331" alt="Image" src="https://github.com/user-attachments/assets/1930d5c6-dbf3-4404-bcda-3aca681662ab" />
On a hunch, I just removed all git worktrees and checked again and now it's populated again. Might be worth checking if that fixes it for you as well. Still a bug though, it worked with git worktrees until a few versions ago.
<img width="1267" height="574" alt="Image" src="https://github.com/user-attachments/assets/75f6d4c3-e181-4e2f-b7e3-8596edc618ab" />
the stupid thing sometimes it works... and sometimes it just empty or freezes straight up(hook issues #23636 , there is another ticket for it)
gotta say the windows version is always breaking...
yolo is just my windows powershell shortcut(notepad $PROFILE) ( function yolo { claude --chrome --dangerously-skip-permissions $args } )
I am having the same issue on Ubuntu. Does not matter from which git / root I run it...
I'm encountering this too (2.1.39 on macOS).
Additional data point (macOS 15, arm64):
Project: 19
.jsonlfiles on disk, 5 real sessions (rest arefile-history-snapshot/summary).sessions-index.jsoncontains all 5 sessionsSo the issue is not just about
sessions-index.jsonbeing incomplete — even sessions that ARE in the index get dropped by the newer resume picker.Workaround:
claude install 2.1.29This 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.
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.
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.
The
/resumesession picker showing empty despite sessions existing on disk? There are three known root causes in v2.1.30+ — including a git worktrees path issue and a hardcoded 10-session batch limit. You can still resume by session ID directly while waiting for a fix: https://cacheoverflow.dev/blog/FdqKCduR