{"version":"2.1.236","anchor":"a-healthy-fullscreen-trial-saves-the-setting-an-explicit-cha","canonical_anchor":"a-healthy-fullscreen-trial-saves-the-setting-an-explicit-cha","heading":"A healthy fullscreen trial saves the setting; an explicit change during it does not","tier":"notice","area":"Fullscreen","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/a-healthy-fullscreen-trial-saves-the-setting-an-explicit-cha","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### A healthy fullscreen trial saves the setting; an explicit change during it does not\n\nA trouble-free fullscreen trial saves the setting, unless you changed it yourself mid-trial.\n\n**What**\n\nWhen a session started under `CLAUDE_CODE_TUI_TRIAL=fullscreen` runs long enough without trouble, `tui: \"fullscreen\"` is written into your user settings. It refuses to write if you set `tui` yourself during the trial, checked both before and inside the queued write, or if the session is not actually running fullscreen, for example because the crash auto-disable fired.\n\n**Details**\n\n- Debug output on the refusal path reads \"fullscreen trial: settings.tui was set explicitly during the trial - not persisting\".\n- A successful save reports `tengu_fullscreen_upsell_trial_persisted` with the session age in milliseconds.\n- The trial variable is read once, unset from the process environment, stripped from respawned child environments, and listed among the variables dropped when switching renderers.\n- The older helper that gated the fullscreen prompt from the fleet view was deleted, though the code that increments the seen count still exists elsewhere.\n\n**Evidence**\n\n`fullscreen trial: settings.tui was set explicitly during the trial \\u2014 not persisting`, `CLAUDE_CODE_TUI_TRIAL`\n\n- Area: Fullscreen\n- Names: `CLAUDE_CODE_TUI_TRIAL`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}