If another live session on your machine already uses the same session name, the newer session yields and takes a suffixed name instead. The check runs at startup, on rename, and again on a delayed recheck. The remote-config flag tengu_session_name_uniqueness controls it and its built-in fallback is on, so without a server value this is active.
- The yielding session logs the change under
[session-name]at info level. - Other sessions it talks to are notified over the local cross-session messaging channel with a message telling them to use the new name.
- Any failure during the check is non-fatal: the session keeps its original name.
tengu_session_name_uniqueness
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
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: 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
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.
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.
New in this build: tengu_session_name_uniqueness