Duplicate session names on one machine now get a suffix automatically, and callers are told the new name.
tengu_session_name_uniqueness Off in both readingsThe 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: off
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's wrong with this entry?
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.
- 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.
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.