tengu_marble_whisper 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.70: no gate table built for this version
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.70. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
The BTW side-question feature, previously hardcoded as disabled (w1(void 0) which was always false), is now properly gated behind the tengu_marble_whisper feature flag.
Feature-flagged via tengu_marble_whisper (default false)
- All three references to the BTW feature (tip display, input parser, spinner tip) now check
gz6()which readstengu_marble_whisper - This means the feature can be enabled server-side without a client update
Feature gate function (search for "tengu_marble_whisper")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.