{"version":"2.1.236","anchor":"restoring-fullscreen-after-a-terminal-ui-switch-now-checks-i","canonical_anchor":"restoring-fullscreen-after-a-terminal-ui-switch-now-checks-i","heading":"Restoring fullscreen after a terminal-UI switch now checks it is allowed","tier":"notice","area":"Terminal UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/restoring-fullscreen-after-a-terminal-ui-switch-now-checks-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Restoring fullscreen after a terminal-UI switch now checks it is allowed\n\nAfter the terminal interface relaunches, fullscreen is only restored where it is actually supported.\n\n**What**\n\nAfter Claude Code relaunches its terminal interface, the handoff telling it which display mode to restore no longer forces fullscreen unconditionally. Fullscreen is now honoured only where alternate-screen rendering is actually eligible.\n\n**Details**\n\n- The mode is carried in `CLAUDE_CODE_TUI_JUST_SWITCHED`.\n- Fullscreen is skipped when running as a local agent, when it has been disabled, or when a crash previously turned it off automatically; the relaunch then forces no particular mode.\n- A value of \"default\" is passed through unchanged.\n\n**Evidence**\n\n`CLAUDE_CODE_TUI_JUST_SWITCHED`\n\n- Area: Terminal UI\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}