{"version":"2.1.232","anchor":"sessions-on-the-same-machine-no-longer-share-a-name","canonical_anchor":"sessions-on-the-same-machine-no-longer-share-a-name","heading":"Sessions on the same machine no longer share a name","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/sessions-on-the-same-machine-no-longer-share-a-name","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Sessions on the same machine no longer share a name\n\nSame-machine name clashes are resolved at startup, on rename and on recheck; the flag defaults on.\n\n**What**\n\nIf 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.\n\n**Details**\n\n- The yielding session logs the change under `[session-name]` at info level.\n- Other sessions it talks to are notified over the local cross-session messaging channel with a message telling them to use the new name.\n- Any failure during the check is non-fatal: the session keeps its original name.\n\n**Evidence**\n\n`tengu_session_name_uniqueness`\n\n- Flag `tengu_session_name_uniqueness`: Off in both readings (read for one account on one subscription tier against v2.1.232; this account: off, anonymous baseline: off, compiled default: 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.\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}