Unclear The finding does not say whether the allowUnattendedServing setting and the stale state each block consent or bypass the check.
Claude Code keeps a stored choice about whether calls can be served remotely while nobody is watching, called unattended serving. The check on that choice was simplified. A call now counts as consented only when the stored choice is exactly "accepted".
Two things take priority over that stored choice:
remoteTools.allowUnattendedServingset tofalsein managed, policy or user settings- a consent state that was left unresolved and has gone stale
Any stored value other than an explicit "accepted" is now treated as no consent. A call is not served unattended because of an unclear or partial answer.
tengu_violin_fret 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.281: 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.281. 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 finding does not say whether the `allowUnattendedServing` setting and the stale state each block consent or bypass the check.