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

Claude Code v2.1.246 ·

Feature flags can explain where their value came from

Flags can explain whether their value came from an override, the server, a cache or the default.

Nothing to try yet In Development
JSON All of v2.1.246
Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
InternalsArea: what it touches
In DevelopmentKind: in v2.1.246,
In DevelopmentSection of the release

A flag-provenance table is built but the check that consults it returns a constant false.

What

A new table turns a flag's origin into a sentence: a local override, the experiment payload fetched this session, the on-disk cache left by an earlier session, the built-in default because experiments are off (a third-party model provider, or telemetry opted out), or the built-in default because the cache was cold. The check that decides whether to consult it is a constant returning false in this build, so the accessor always reports the default path.

Evidence

from GrowthBook (the disk cache of an earlier session)

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

See this entry in the whole of v2.1.246 →

Feedback