{"version":"2.1.287","anchor":"update-relaunch-preserves-conversation-and-records-update","canonical_anchor":"update-relaunch-preserves-conversation-and-records-update","heading":"Relaunching after \/update keeps the conversation when the last reply wasn't saved","tier":"notice","area":"Updates","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/update-relaunch-preserves-conversation-and-records-update","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Relaunching after `\/update` keeps the conversation when the last reply wasn't saved\n\nIf Claude's last reply could not be saved, relaunching after `\/update` now resumes the conversation instead of starting a fresh one\n\n**Unclear.** It is not clear exactly when the transcript is treated as failed to save.\n\n**What**\n\nAfter `\/update`, Claude Code relaunches itself on the new version. Before this change, the relaunch started a fresh conversation if there was no saved transcript, which is the saved record of the conversation.\n\nThe relaunch now checks first whether the transcript failed to save. If Claude's last response could not be saved, Claude Code adds a `\/update` entry to the transcript and resumes the conversation. It shows the message \"Claude's last response couldn't be saved, so it may be missing.\"\n\n**Why**\n\nUpdating is less likely to cost you your conversation. The warning also tells you that the last reply may be missing after the restart.\n\n- Area: Updates\n- Names: `\/update`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}