Accepting the fullscreen renderer prompt no longer writes the setting straight away. Claude Code relaunches into a trial and only saves tui: "fullscreen" if the session stays healthy. Separately, each fullscreen launch is recorded before the first frame and cleared 10 seconds after it; a launch that dies first counts as a strike, and 2 strikes disable fullscreen on that machine for that version. /tui fullscreen retries, and CLAUDE_CODE_NO_FLICKER=1 still overrides.
- The renderer decision gained two new reasons:
upsell_trial_onfor a trial session andcrash_auto_offfor the self-disable. - Strike state lives in the global config as
fullscreenBootPending,fullscreenBootStrikesandfullscreenAutoDisabled, the last stamped with the build version (2.1.236). While the stamp matches the running version fullscreen stays off and the upsell is suppressed; an update clears it. - One strike falls back to the classic renderer for that launch only. Pending records go stale after 10 minutes on the same host, 30 days across hosts.
- The canary applies to interactive sessions entering fullscreen via settings, trial, the Anthropic default, or the downsell/gb paths. It is skipped for env-forced fullscreen and when
CLAUDE_CODE_EXIT_AFTER_FIRST_RENDERis set. - When it trips, stderr says: "Claude Code's fullscreen renderer has repeatedly failed to start on this machine, so it has been turned off here. Run /tui fullscreen to try it again (this also resets after an update)."
- Bare
/tuinow explains why the classic renderer is active, distinguishing a sticky repeated-failure disable from a single unfinished launch. - Telemetry:
tengu_fullscreen_crash_auto_off, carrying sticky, strikes, new_strikes, pending age and the entry path fullscreen would have used. - Neither path is behind a remote flag. Fullscreen-by-default itself still sits behind
tengu_amber_creekandtengu_pewter_brook, both falling back to off.
crashAutoOff: !1,, crash_auto_off, Claude Code's fullscreen renderer has repeatedly failed to start on this machine, so it has been turned off here. Run /tui fullscreen to try it again (this also resets after an update)., (fullscreen was turned off on this machine after it repeatedly failed to start; /tui fullscreen retries), tengu_fullscreen_crash_auto_off, upsell_trial_on
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_amber_creek Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.236: off
tengu_pewter_brook Off by default, switched on for this accountThe shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.
This account: on · anonymous baseline: on · compiled default in v2.1.236: off
Read once, for one account on one subscription tier, against v2.1.236. It isn't a statement about your account. What a flag value here can and cannot tell you
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.