{"version":"2.1.248","anchor":"sessions-record-where-their-name-came-from","canonical_anchor":"sessions-record-where-their-name-came-from","heading":"Sessions record where their name came from","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/sessions-record-where-their-name-came-from","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Sessions record where their name came from\n\nSessions now record whether you named them or a peer process did.\n\n**What**\n\nA session's identity record now tracks whether its name was chosen by you or handed down by another process. At startup the name is tagged `user` when you supplied it and `peer` when it was inherited from a peer process, and a separate user-chosen flag is set when the name came from you directly or from resolving a collision on a name you typed. Nothing in this build changes what you see; the origin is only recorded.\n\n**Details**\n\n- The origin tag is decided by the same check that determines whether the session is interactive, so a session with no interactive parent is treated as having a user-supplied name.\n- The user-chosen flag stays true when your typed name collided with an existing one and was resolved to a variant, so disambiguation does not make the name look machine-generated.\n- No setting, flag or environment variable exposes either value yet, and no behaviour is currently gated on them.\n\n**Evidence**\n\n`sessionNameArgSource: xU() === void 0 ? \"user\" : \"peer\",`, `nameIsUserChosen`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}