A blank CLAUDE_CODE_SESSION_NAME now falls back to the directory-derived name.
What's wrong with this entry?
A name set through CLAUDE_CODE_SESSION_NAME is passed through a normalizer, and if the result is empty an interactive session falls back to the name derived from the working directory rather than registering a blank one.
- The session pid file now also records where the name came from and a timestamp for when it was set; the recorded source in this build is the derived one.
CLAUDE_CODE_SESSION_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
Session titles are normalised and blank titles rejected
Both mention name
-
v2.1.221
Background session names starting with "-" survive respawn
Both mention name
-
v2.1.223
Cloud sessions started with a title rename themselves instead of auto-titling
Both mention name