Unclear The finding does not say what the new condition function actually evaluates or when it newly triggers versus the old one.
The system message that tells Claude "You are operating autonomously. The user is not watching in real time... asking will block the work" is now shown when either of two conditions is true. The second condition now receives the message/state argument, whereas before it was checked with no arguments at all.
By giving the second check access to the current state, the decision of whether to show this autonomous-operation guidance can now depend on details of the ongoing session rather than being a fixed, context-free check.
tengu_amber_sextant 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.275: 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.275. It isn't a statement about your account. What a flag value here can and cannot tell you
The finding does not say what the new condition function actually evaluates or when it newly triggers versus the old one.