{"version":"2.1.295","anchor":"relaunch-failure-now-logs-and-resets-terminal-state","canonical_anchor":"relaunch-failure-now-logs-and-resets-terminal-state","heading":"A failed relaunch is now logged and leaves the terminal tidy","tier":"notice","area":"Updates","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/relaunch-failure-now-logs-and-resets-terminal-state","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### A failed relaunch is now logged and leaves the terminal tidy\n\nIf Claude Code fails to restart itself, the error is now logged and the terminal is reset instead of the error being printed raw\n\n**What**\n\nWhen Claude Code tries to restart itself and the restart fails, the error used to be printed straight to the terminal as \"Failed to relaunch Claude Code: ...\". It is now logged as \"Failed to relaunch:\" instead, and the terminal's display state is reset. The reset is done differently when the restart was for resuming an earlier session than for other restarts.\n\n**Why**\n\nThis changes how a failed restart is reported, and the reset aims to leave your terminal usable afterwards.\n\n- Area: Updates\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}