tengu_bridge_partial_messages falls back to false.
A code path that used to be controlled by the tengu_kairos_loop_dynamic flag is now controlled by tengu_bridge_partial_messages. Its built-in fallback is false, so unless Anthropic's remote config sends a value, the partial-message bridging path stays off.
return x("tengu_bridge_partial_messages", !1);
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_kairos_loop_dynamic On for this account, and not off by defaultThe 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.248: not a boolean we can read
tengu_bridge_partial_messages Not enough to sayNothing 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.248: off
Read once, for one account on one subscription tier, against v2.1.248. It isn't a statement about your account. What a flag value here can and cannot tell you
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.
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.
New in this build: tengu_bridge_partial_messages