tengu_ax_screen_reader Gate removed from the codeThis release deleted the gate from the code while it was still reading on for the account this site reads, so the code path no longer asks a flag before running.
This account: on · anonymous baseline: on · compiled default in v2.1.206: not a boolean we can read
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.206. 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 screen reader mode status indicator now shows how the mode was activated (e.g., via environment variable or CLI flag) rather than just showing it's on.
- Old:
[Accessible screen reader mode: on] - New:
[Screen Reader Mode: on via {source}]when an activation source is known, or[Screen Reader Mode: on]otherwise. - The three possible
{source}values are:"flag"(when the--ax-screen-readerCLI flag is passed),"env"(when theCLAUDE_AX_SCREEN_READERenvironment variable is set to a truthy value), and"settings"(whenaxScreenReader: trueappears in the settings file). The priority order is flag → env → settings. - Activation is additionally gated by the GrowthBook feature flag
tengu_ax_screen_reader. If the flag disables the feature, screen reader mode does not activate regardless of the CLI flag, env var, or settings value, andactivationSource()returnsundefined— so theon via {source}suffix will not appear even if an activation mechanism is present. - When the GrowthBook resolver is not yet available (e.g., before first-party initialization), the check defaults to
true, allowing the mode to activate locally without a network round-trip.
New format (search for "[Screen Reader Mode: on via"); activation sources (search for "activationSource()"); GrowthBook flag (search for "tengu_ax_screen_reader")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.