If another live session already holds your session name, yours gets renamed and both you and Claude are told.
What's wrong with this entry?
If another Claude Code session running on the same machine already holds the name you asked for, this session takes an adjusted name instead of silently overwriting. You get a notice ending "Use /rename to pick a different name.", and the model is told the same thing so it does not refer to the old name.
- The saved session record now tracks where its name came from, with a new "collision" value alongside "user", "auto" and "derived", and keeps the names it previously held.
- The model-facing reminder says another live session on this machine already holds that name, so this session is renamed.
- Telemetry records a session name collision, including a variant for when the collision check itself failed.
another live session on this machine already holds that name, so this session is, Use /rename to pick a different name.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.221
Renaming a session propagates the new name
Both mention rename
-
v2.1.221
/rename rejects names that resolve to nothing
Both mention rename
-
v2.1.248
/list-agents can withhold session names and directories
Both mention rename