/resume slash command shows "No conversations found to resume" despite sessions existing on disk

Resolved 💬 7 comments Opened Apr 16, 2026 by USerik Closed Jun 4, 2026

Description

The /resume slash command inside an active Claude Code session returns "No conversations found to resume." even though conversation files exist on disk and claude --resume <id> works correctly from the CLI.

Steps to Reproduce

  1. Start a Claude Code session in a project directory
  2. End the session (or let it close)
  3. Start a new Claude Code session in the same directory
  4. Type /resume inside the session

Result: No conversations found to resume.

Expected: A list of recent sessions to choose from

Environment

  • OS: macOS Darwin 25.3.0 (Apple Silicon M4)

Investigation

Sessions do exist on disk under ~/.claude/projects/. The claude --resume <id> command from terminal works correctly with the same session ID.

Hypothesis

The projects directory may contain two path variants that differ only in case (e.g. capital vs lowercase letter in directory name). The /resume command may be deriving the project path from pwd and producing a different case than the one used when the session was originally stored — causing a lookup miss.

Workaround

Use claude --resume <session-id> directly from the terminal. The session ID can be found in the directory name under ~/.claude/projects/<project-path>/.

View original on GitHub ↗

This issue has 7 comments on GitHub. Read the full discussion on GitHub ↗