{"version":"2.1.251","anchor":"auto-mode-can-exit-itself-and-tell-you-why","canonical_anchor":"auto-mode-can-exit-itself-and-tell-you-why","heading":"Auto mode can exit itself and tell you why","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/auto-mode-can-exit-itself-and-tell-you-why","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Auto mode can exit itself and tell you why\n\nIf your org's settings ban auto mode here, Claude Code exits it and tells you why.\n\n**What**\n\nIf your organization's managed settings disable auto mode for the kind of session you are in, Claude Code now leaves auto mode during its normal permission refresh and posts a notice in the conversation pointing at settings, rather than staying in a mode policy forbids.\n\n**Details**\n\n- Triggers when the current mode is auto, or plan with auto queued up behind it, and the managed policy check says auto is not allowed here.\n- Skipped when admin policy settings failed to load with a non-warning error, unless the admin-survivor fallback is active.\n- Auto mode itself is controlled by the `tengu_auto_mode_config` gate, which resolves to enabled when the server sends no value.\n\n**Evidence**\n\n`exitedAutoMode`\n\n- Flag `tengu_auto_mode_config`: Not enough to say (read for one account on one subscription tier against v2.1.251; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read)\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}