Auto mode lets Claude go ahead with more actions without asking you first. In some sessions, when CLAUDE_CODE_REMOTE is not set, Claude Code can choose auto mode as the starting mode. Non-interactive sessions, such as headless runs or ones driven through the SDK, need an extra condition to get this. One way to meet it is a server-controlled switch, and that switch now falls back to off instead of on when the server sends nothing.
So when the server gives no value, non-interactive sessions no longer start in auto mode this way. Setting CLAUDE_CODE_BRIDGE_CHILD_AUTO_DEFAULT still forces auto mode as the default. Interactive sessions are not affected by this switch.
In readings taken before this release, the flag server returned off for this switch for this site's account and for an anonymous baseline.
Scripts and automated runs are less likely to start with fewer permission prompts than you expect. If you relied on auto mode being the default there, set CLAUDE_CODE_BRIDGE_CHILD_AUTO_DEFAULT or choose the mode yourself.
tengu_moss_anchor Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.302: off
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.302. It isn't a statement about your account. What a flag value here can and cannot tell you