{"version":"2.1.232","anchor":"session-naming-has-explicit-outcomes-when-two-sessions-want-","canonical_anchor":"session-naming-has-explicit-outcomes-when-two-sessions-want-","heading":"Session naming has explicit outcomes when two sessions want the same name","tier":"soon","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/session-naming-has-explicit-outcomes-when-two-sessions-want-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Session naming has explicit outcomes when two sessions want the same name\n\nTwo sessions wanting the same name now resolve through fixed outcomes deciding who keeps or yields it.\n\n**What**\n\nClaiming a session name now resolves to one of a fixed set of outcomes (\"own-name\", \"held\", \"yielded\", \"kept\", \"superseded\", \"pre-decided\"), and that outcome decides whether the name is recorded as user-chosen, auto-generated or a collision, whether the session announces that it gave the name up, and whether the old name is kept for the session list. Part of the cross-session naming machinery, whose availability is set by remote config.\n\n**Evidence**\n\n`pre-decided`\n\n- Area: Cross-Session Messaging\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}