Session auto-name not usable in /resume — misleading UX

Resolved 💬 3 comments Opened Apr 6, 2026 by Mirksen Closed Apr 10, 2026

Problem

Sessions get an auto-generated name (e.g. "deterministic-drift-fixes") shown in the title/status bar. This suggests the name is a useful identifier you can use to find and resume sessions later.

However, /resume lists sessions by timestamp and working directory — the auto-generated name is not searchable, not shown in the resume list, and not usable as a lookup key.

Why this is confusing

  1. User sees session name → assumes it's meaningful
  2. User remembers the name for later
  3. User runs /resume → name is nowhere to be found
  4. User has to scan by timestamp instead

The auto-name creates a false sense of identity. It looks like a feature but doesn't connect to anything.

Expected behavior

Either:

  • Option A: Show the auto-name in /resume list and make it searchable/filterable
  • Option B: Don't auto-generate a name at all (avoid the false signal)

Note: /rename exists as a manual workaround and works fine — but the auto-name undermines it by suggesting naming is already handled.

Environment

  • Claude Code CLI (Claude Max)
  • macOS

View original on GitHub ↗

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