[Bug] /rename session title not persisted - renamed sessions don't appear in resume list

Resolved 💬 4 comments Opened Feb 8, 2026 by tobedoit Closed Mar 9, 2026

Description

After renaming a session with /rename, the custom title is not saved to the session index. When trying to resume later, the renamed session doesn't appear in the resume list and cannot be found by searching the custom name.

Steps to Reproduce

  1. Start a Claude Code session
  2. Run /rename my-custom-name
  3. Confirm rename succeeds (stdout: Session renamed to: my-custom-name)
  4. Exit the session (/exit)
  5. Run claude and open the resume picker
  6. Search for "my-custom-name" → not found
  7. The session appears with its first message or slug instead of the custom name

Expected Behavior

  • Renamed sessions should appear with their custom title in the resume list
  • Searching by the custom name should find the session
  • claude --resume "my-custom-name" should work

Actual Behavior

  • The /rename command reports success
  • The rename is recorded in ~/.claude/history.jsonl
  • But the session metadata/index is NOT updated with the new title
  • The session still appears with its auto-generated slug (fluffy-yawning-tome) or first message
  • The session can only be resumed by its UUID: claude --resume <session-id>

Investigation

  • Session file exists: ~/.claude/projects/.../c8052f02-...jsonl
  • History shows the rename command was executed with correct sessionId
  • Session transcript shows slug: "fluffy-yawning-tome" — no custom title field found
  • The rename metadata was never written to the session index

Environment

  • Claude Code version: 2.1.37
  • OS: macOS (Darwin 25.2.0, arm64)
  • Terminal: Ghostty
  • Installation: Native binary (~/.local/bin/claude)

View original on GitHub ↗

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