claude-code - 💡(How to fix) Fix /resume slash command shows "No conversations found to resume" despite sessions existing on disk [1 comments, 2 participants]

TL;DR

The /resume command in Claude Code may be failing due to case sensitivity issues in project directory paths, and using claude --resume <session-id> from the terminal is a viable workaround.

Guidance

• Verify that the project directory path used by the /resume command matches the case of the directory path where sessions are stored, as case differences may cause the lookup to fail.
• Check the ~/.claude/projects/ directory for sessions with IDs that can be used with claude --resume <session-id> to confirm that sessions are being stored correctly.
• Consider normalizing the project directory path to ensure consistency in case, potentially by setting a specific case (e.g., lowercase) for all project directories.
• If using claude --resume <session-id> works, it indicates that the issue is likely with how the /resume command resolves project paths.

Example

No specific code example is provided as the issue seems related to directory path case sensitivity rather than code syntax.

Notes

The provided hypothesis suggests a case sensitivity issue, which is plausible given the difference in behavior between the /resume command and claude --resume <session-id>. However, without direct access to the code or more detailed debugging information, this remains an educated guess.

Recommendation

Apply workaround: Using claude --resume <session-id> from the terminal is a reliable method to resume sessions when the /resume command fails, indicating that the sessions are stored correctly but the command has issues resolving the project path due to case sensitivity.