The one-time auto-mode default prompt and its startup check are wired up but off unless remote config turns them on.
Claude Code can now ask, once, whether you want auto mode to become your default permission mode, and the interactive session checks at startup whether to queue that question behind whatever is already on screen. The prompt takes an accepted, declined or cancelled answer. Both the prompt and the startup check are present in this build but switched off, so nothing appears unless remote config turns them on.
- Gated on the remote flag
tengu_maple_pier, which falls back to off, so the prompt is invisible by default in this build. - Shows at most once ever, tracked by
hasSeenAutoDefaultNudgein config, and only after onboarding is complete. - The startup check returns nothing unless
hasSeenAutoDefaultNudgeis unset and your user settings set apermissions.defaultModeto something other than auto, with no project, local, command-line or policy setting overriding it. - Editor and SDK hosts can drive the flow: the VS Code notifications
auto_default_nudge_shownandauto_default_nudge_resolvednow go to a dedicated handler rather than being logged as generic events. - A second dialog kind,
ide_onboarding, is registered alongside it.
choose: make auto mode the default permission mode, tengu_maple_pier
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_maple_pier 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.236: off
Read once, for one account on one subscription tier, against v2.1.236. It isn't a statement about your account. What a flag value here can and cannot tell you
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.