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.232 ·

Session names are made unique across live sessions on the same machine

Duplicate session names on one machine now get a suffix automatically, and callers are told the new name.

You'll notice New Features
JSON All of v2.1.232
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
New FeaturesKind: in v2.1.232,
New FeaturesSection of the release
What

If you name a session and another session running on the same machine already goes by that name, the new one yields the name, takes a suffixed variant, and warns you. Anything already talking to that session over its local socket is told the new name so it keeps addressing the right one. Turned on by the remote flag tengu_session_name_uniqueness, whose built-in fallback is on.

Details
  • The outcome of each naming attempt is recorded as one of: kept the name, held it, yielded it, was superseded, or already decided earlier.
  • Startup checks the name you passed in, re-checks interactively, and runs the same check again on rename; names supplied by hooks are checked against the yield record before being applied or cached.
  • The registry of live sessions now also records when each name was taken.
  • If the registry cannot be read, the notice to other sessions is skipped and a debug line is logged instead.
Evidence

is held by another live session on this machine). Address this one as , Another live session on this machine goes by "

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

Read from
Feature flag
tengu_session_name_uniqueness Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.232: on

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.232. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns off for tengu_session_name_uniqueness, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_session_name_uniqueness, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_session_name_uniqueness

See this entry in the whole of v2.1.232 →

Feedback