The setting tengu_ccr_v2_send_events_cli, which selects the newer path for sending cloud session events, now falls back to enabled when the server expresses no opinion. It previously fell back to disabled. The real value still comes from remote config.
- Nothing else in the bundle references the local name of the check, so which send path this default now turns on cannot be pinned down from the build alone.
- Related churn in the cloud sessions client in the same change threads a per-call timeout through event posts and control responses, consistent with the v2 path being prepared for real traffic.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_ccr_v2_send_events_cli 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.247: on
Read once, for one account on one subscription tier, against v2.1.247. 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.