Relay message classification gained an origin named "hearth_human", counted as a human turn only when a gate allows it. The gate reads the remote flag tengu_cuddly_willow, which falls back to true, so with no remote value set the origin is honoured.
- Two telemetry events accompany it: "bridge_projects_human_origin" when the origin is accepted, and the same name logged as rejected with reason "disabled_by_flag" when the gate is off.
- Neither the origin nor the gate name existed in the previous build.
bridge_projects_human_origin
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_cuddly_willow 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.233: on
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.233. 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_cuddly_willow