You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SessionsArea: what it touches
ImprovementsKind: in v2.1.309,
ImprovementsSection of the release
Unclear It is not clear when Claude Code gives a session an automatic name.
What
A session is one Claude Code conversation, and each can have a name. Several parts of how those names are set have changed:
Automatic names are now started with the source "auto", so Claude Code knows a name was generated rather than chosen. This is skipped when the session was started with an SDK URL (sdkUrl).
The check on the current session name now also requires that its source is not "auto".
A name given when the session is launched is kept when the keepLaunchName option is set.
An automatic rename no longer overwrites a name that changed in the meantime.
The list of live sessions now leaves out other processes' sessions that share this session's id.
When the check that a name is unique fails, the current name is kept.
Why
Before, automatic renames could replace a name that had changed in the meantime, and the live list included every session. In practice, a name you set or gave at launch should now stay put instead of being swapped for a generated one.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear when Claude Code gives a session an automatic name.
