[BUG] /rename command is self-defeating

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

• I used /rename to give my session a name so that I could solve another issue, and easily come back
• I then immediately issued /clear, and fixed an issue
• I used /exit, and then claude --resume
• The list of sessions listed my session name on 3 different entries, all with different sized and ages

Further, I was unable to use the UI to select any session; the selected line continuously danced between two of the options and I could not do anything els. I'm guessing the name is used to track which one it's pointing at, which would require the names be unique, but I can't say for sure.

What Should Happen?

The name I assign with /rename should only ever be associated with THAT ONE SESSION, and subsequently starting a new session or using /clear shuld abandon that name.

The whole point of naming a session is so that you can distinguish it from other sessions. Any other behavior is nonsensical.

Error Messages/Logs

❯ add-sideband-structure
    23 minutes ago · v2 · 4.3KB

    add-sideband-structure
    3 hours ago · v2 · 166.8KB

    add-sideband-structure
    4 hours ago · v2 · 1.4MB

Steps to Reproduce

1. Assign a name with /rename
2. Use /clear or restart with a new session
3. Restart with claude --resume

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.143 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_