[BUG] /resume doesn't show unnamed sessions after using /rename

Resolved 💬 3 comments Opened Feb 4, 2026 by ljh740 Closed Feb 7, 2026

Bug Description

After using the /rename command to rename some sessions, the /resume command no longer displays unnamed (non-renamed) sessions in the picker. Only renamed sessions are visible.

Steps to Reproduce

  1. Have multiple active sessions (some with default names, some potentially renamed)
  2. Use /rename command to rename one or more sessions
  3. Use /resume command to view available sessions
  4. Observe that only renamed sessions appear in the picker

Expected Behavior

The /resume command should display all available sessions, including:

  • Renamed sessions (with custom names)
  • Unnamed sessions (with default/auto-generated names)

Actual Behavior

After using /rename, the /resume picker only shows renamed sessions. Unnamed sessions are no longer visible or accessible through the picker.

Environment

  • Claude Code Version: 2.1.31
  • Operating System: macOS 26.2
  • Interface: CLI

Additional Context

  • The unnamed sessions may still exist in the session storage directory
  • This appears to be a filtering or indexing issue rather than data loss
  • Workaround: Unknown - unable to access unnamed sessions after rename operation

Impact

This prevents users from accessing their unnamed sessions after performing any rename operation, potentially causing loss of work context.

View original on GitHub ↗

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