Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.239 Home All releases ←olderv2.1.238 v2.1.240newer→
Claude Code v2.1.239

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

You'll notice
Useful4 Signal3
Rendering not in their notes

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

Feature flag
tengu_pewter_brook On for this account, and not off by default

The flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.

This account: on · anonymous baseline: on · compiled default in v2.1.239: on

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: on

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

DISABLE_GROWTHBOOK
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.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.239 →