Messages arriving through the new hearth_human relay origin are now treated as sent by a human, joining slack_human, teams_human and owner_relay. That decides idle-activity notes, whether a message is recorded as from a human or a peer, and the verified-human turn marking in remote-worker and bridge sessions. The extra origin only counts when the tengu_cuddly_willow flag is on; its built-in fallback is on, so absent a server override this path is live.
- The flag is threaded through the classification helpers as an extra argument, so each caller decides whether to accept the new origin.
- The previous build defined
hearth_humanbut no check consulted it.
hearth_human, tengu_cuddly_willow
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