{"version":"2.1.305","anchor":"auto-mode-permission-dialog-gated-by-tengu-sable-orrery","canonical_anchor":"auto-mode-permission-dialog-gated-by-tengu-sable-orrery","heading":"Auto mode startup dialog sets and restores a setting around itself","tier":"internal","area":"Auto Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/auto-mode-permission-dialog-gated-by-tengu-sable-orrery","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Auto mode startup dialog sets and restores a setting around itself\n\nBehind a server-controlled switch, the auto mode startup dialog now changes some state before it shows and restores it after\n\n**Unclear.** It is not stated what state is changed around the dialog.\n\n**What**\n\nAuto mode is a permission mode in which Claude Code approves actions without asking you. The dialog Claude Code shows at startup for this now does an extra step behind a server-controlled switch, `tengu_sable_orrery`. Before the dialog appears, Claude Code turns some state on, and after the dialog closes it puts that state back as it was. The switch is on unless it is turned off remotely.\n\nBefore, the dialog appeared with no step before or after.\n\n**Why**\n\nThe startup dialog for auto mode behaves differently when this switch is on.\n\n- Flag `tengu_sable_orrery`: Not enough to say (read for one account on one subscription tier against v2.1.305; this account: no value returned, anonymous baseline: no value returned, compiled default: 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.\n- Area: Auto Mode\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}