Source Intelligence

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.235 Home All releases olderv2.1.234 v2.1.236newer
Claude Code v2.1.235

A flag served as false is now distinguished from a flag never set

Under the hood
Useful1 Signal3
Internals

The tool can now tell a feature switched off remotely from one that was never set at all.

Feature flag
tengu_violin_wood Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

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

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

What

A new check reports whether a remote feature flag was actively served as off, as opposed to simply having no value and falling back to a local default. The device bridge uses it to decide whether to keep running, logging stopping: the gate turned off with reason gate_off.

Details
  • Returns true only when the off value came from the served payload, a local override, or an explicit disable; a value read from a cached file on disk counts as false, and a pure local fallback defers to a separate check.
  • Applied to the flag tengu_violin_wood, which is read with a fallback of false.
Evidence

isViolinWoodServedOff

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.235 →