{"version":"2.1.319","anchor":"rename-failure-messages-now-distinguish-transcript-and-regi","canonical_anchor":"rename-failure-messages-now-distinguish-transcript-and-regi","heading":"\/rename now warns when the new name might not stick","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/rename-failure-messages-now-distinguish-transcript-and-regi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### `\/rename` now warns when the new name might not stick\n\nIf `\/rename` cannot save the new name to the session transcript, it now warns the name may not last and suggests running it again\n\n**What**\n\n`\/rename` gives the current session a name. Claude Code saves that name in two places: the session transcript, which is the saved record of the conversation, and the session registry, which other sessions read.\n\nIf the transcript could not be updated, `\/rename` now says \"The new name may not last: the session transcript could not be updated\" and suggests running `\/rename` again. The existing warning that other sessions may still show the old name, when the registry could not be updated, is still shown.\n\n**Why**\n\nA rename that failed to save used to pass without a word, so the old name could quietly come back. Now you can see it and try again.\n\n- Area: Sessions\n- Names: `\/rename`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}