{"version":"2.1.301","anchor":"session-alias-recording-skippedredirected-in-a-mode","canonical_anchor":"session-alias-recording-skippedredirected-in-a-mode","heading":"Session names can be saved somewhere other than the local alias file","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/session-alias-recording-skippedredirected-in-a-mode","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Session names can be saved somewhere other than the local alias file\n\nWhen a certain condition holds, Claude Code now saves a session's alias through a different route instead of the local alias file\n\n**Unclear.** It is not clear what condition makes Claude Code store the alias elsewhere, or where it goes.\n\n**What**\n\nA session is one conversation with Claude Code, and it can be given an alias, a short name you can use to find it again. Claude Code used to always write these aliases to a local file. When a certain condition holds, it now passes the alias to a different storage route instead.\n\n**Why**\n\nThis may be a way to store session names in a remote or alternative place.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}