Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.248 ·

Sessions record where their name came from

Sessions now record whether you named them or a peer process did.

Under the hood In Development
JSON All of v2.1.248
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
SessionsArea: what it touches
In DevelopmentKind: in v2.1.248,
In DevelopmentSection of the release
What

A session's identity record now tracks whether its name was chosen by you or handed down by another process. At startup the name is tagged user when you supplied it and peer when it was inherited from a peer process, and a separate user-chosen flag is set when the name came from you directly or from resolving a collision on a name you typed. Nothing in this build changes what you see; the origin is only recorded.

Details
  • The origin tag is decided by the same check that determines whether the session is interactive, so a session with no interactive parent is treated as having a user-supplied name.
  • The user-chosen flag stays true when your typed name collided with an existing one and was resolved to a variant, so disambiguation does not make the name look machine-generated.
  • No setting, flag or environment variable exposes either value yet, and no behaviour is currently gated on them.
Evidence

sessionNameArgSource: xU() === void 0 ? "user" : "peer",, nameIsUserChosen

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.248 →

Feedback