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

Device bridge stops when its gate is served off, not merely unset

Device bridge now stops only when its gate is explicitly served off, not merely absent

Under the hood Nothing to try yet In Development
JSON All of v2.1.235
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Device BridgeArea: what it touches
In DevelopmentKind: in v2.1.235,
In DevelopmentSection of the release

A new helper distinguishes a remote-config value of false from the absence of any value at all. It reports true only when the off value actually came from the payload, an override, or a disabled source, falling back to a separate check for local-fallback values and returning false when the value is read from disk.

The device bridge now uses this helper as its liveness predicate, logging stopping: the gate turned off with reason gate_off when it is triggered.

Read from
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: off

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 has happened since
Flag reading moved The flag server now returns off for tengu_violin_wood, 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_violin_wood, 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.235 →

Feedback