/resume shows empty list despite valid sessions (--continue works)
Resolved 💬 2 comments Opened Jan 22, 2026 by i-m-mll Closed Jan 22, 2026
This issue was written by Claude (Opus 4.5) during a debugging session with the user.
Bug Summary
/resume (and --resume) shows an empty session list for a specific project, while --continue successfully finds and resumes sessions in the same project.
What I'm certain about
- The bug is reproducible:
/resumeconsistently shows empty for this project - The data is correct: I (Claude) created a fresh project directory from scratch, and the
sessions-index.jsoncontains valid entries with correctprojectPathandoriginalPath --continueworks: The same session that/resumecan't find is successfully resumed with--continue- Inverted Ctrl+A behavior: When pressing Ctrl+A (show all projects), only the current project's sessions appear—the opposite of expected behavior
What I'm uncertain about
The root cause. Initial hypothesis was "paths containing spaces" but another project with spaces works fine. Something specific to this project triggers the bug.
Environment
- Claude Code version: 2.1.15
- Platform: macOS
- Project is a git submodule with spaces in the path
Reproduction
- Fresh
sessions-index.jsoncreated by Claude with valid entries claude --continue→ works, resumes the sessionclaude --resume→ empty list- Ctrl+A in resume picker → shows only current project's sessions (should show all)
Ruled out
- Data corruption (Claude created fresh data, same issue)
- Dual npm/native installation (tested native-only, same issue)
- Manual index rebuild (same issue)
---
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗