{"version":"2.1.248","anchor":"more-session-name-origins-survive-a-reload","canonical_anchor":"more-session-name-origins-survive-a-reload","heading":"More session-name origins survive a reload","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/more-session-name-origins-survive-a-reload","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### More session-name origins survive a reload\n\nSession names set by you, a peer, a hook or automatically keep their origin after reload.\n\n**What**\n\nSession metadata now keeps the record of where a session name came from for `user`, `peer`, `auto` and `hook` origins, not just `derived` and `collision`. Names set by those paths are no longer silently downgraded when the session is read back.\n\n**Evidence**\n\n`nameSource`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}