Unclear It is not clear what the new marker or the prompt-screening step changes for someone using Claude Code.
In auto mode, Claude Code uses a separate check, called a classifier, to decide whether an action can go ahead without asking you. The information passed to that check can now include an extra on-or-off marker in some cases. Claude Code also gained a new step for screening prompts in the interactive session.
Neither change is described as altering what you see. They change what information is available when Claude Code decides how to handle a prompt or an action.
tengu_ax_screen_reader 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.295: 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.295. It isn't a statement about your account. What a flag value here can and cannot tell you
The code path no longer asks a flag before it runs.
The code path no longer asks a flag before it runs.
It is not clear what the new marker or the prompt-screening step changes for someone using Claude Code.