{"version":"2.1.236","anchor":"a-crash-in-the-display-now-exits-with-an-explanation-instead","canonical_anchor":"a-crash-in-the-display-now-exits-with-an-explanation-instead","heading":"A crash in the display now exits with an explanation instead of a raw stack trace","tier":"use","area":"Terminal UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/a-crash-in-the-display-now-exits-with-an-explanation-instead","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### A crash in the display now exits with an explanation instead of a raw stack trace\n\nInterface crashes now print a readable message and tell you the classic-renderer env var.\n\n**What**\n\nIf the code drawing the interface throws and cannot recover, Claude Code prints a message saying it exited after an interface error. When the fullscreen renderer was still starting up, it also says the next launch will use the classic renderer and that `CLAUDE_CODE_DISABLE_ALTERNATE_SCREEN=1` forces that renderer.\n\n**Details**\n\n- Applies to normal interactive use. SDK and debug paths still rethrow the original error so tooling can see it.\n\n**Evidence**\n\n`Claude Code exited after an unrecoverable interface error`\n\n- Area: Terminal UI\n- Names: `CLAUDE_CODE_DISABLE_ALTERNATE_SCREEN=1`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5"}