{"version":"2.1.70","anchor":"btw-side-questions-gating-feature-flagged","canonical_anchor":"btw-side-questions-gating-feature-flagged","heading":"BTW Side Questions Gating [Feature-Flagged]","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.70\/e\/btw-side-questions-gating-feature-flagged","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.70","markdown":"### BTW Side Questions Gating [Feature-Flagged]\n\n**What**\n\nThe 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.\n\n**Status**\n\nFeature-flagged via `tengu_marble_whisper` (default `false`)\n\n**Details**\n\n- All three references to the BTW feature (tip display, input parser, spinner tip) now check `gz6()` which reads `tengu_marble_whisper`\n- This means the feature can be enabled server-side without a client update\n\n**Evidence**\n\nFeature gate function (search for `\"tengu_marble_whisper\"`)\n\n- Flag `tengu_marble_whisper`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.70; this account: on, anonymous baseline: on, compiled default: 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."}