Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.239 ·

Fullscreen rendering turns on by default for fresh installs when remote config is unavailable

Fresh installs without remote config now start with the flicker-free fullscreen renderer on.

You'll notice No documentation found Improvements
JSON All of v2.1.239
You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
RenderingArea: what it touches
ImprovementsKind: in v2.1.239,
What probably matters to youSection of the release
What

On a fresh install where remote experiment config is not consulted, the flicker-free fullscreen renderer now starts on instead of off. This covers clients running with DISABLE_GROWTHBOOK, non-first-party setups and telemetry-off configurations. The fullscreen upsell is also suppressed when remote config is live but the client only ever saw its local fallback value, so it no longer nags people whose experiment value never arrived.

Details
  • The new branch requires all three: remote config not in play, a recorded first-start version, and the fullscreen upsell having been shown fewer than 3 times.
  • The diagnostic value for this path is fresh_install_on, sitting alongside the existing downsell_on and gb_on.
  • The two experiment gates tengu_pewter_brook and tengu_amber_creek still fall back to off; the fresh-install branch runs ahead of them and bypasses both.
  • The gate lookup now also records where the value came from, which is what lets the upsell tell a real remote value from a local default.
Evidence

fresh_install_on

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundleDISABLE_GROWTHBOOK
Feature flag
tengu_pewter_brook Off by default, switched on for this account

The 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.239: off

tengu_amber_creek Not enough to say

Nothing 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.239: off

Read once, for one account on one subscription tier, against v2.1.239. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns on for tengu_pewter_brook, read as this 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.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_pewter_brook, read as this 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.

See this across every release →

See this entry in the whole of v2.1.239 →

Feedback