{"version":"2.1.288","anchor":"auto-mode-off-explanation-text-for-permission-prompts","canonical_anchor":"auto-mode-off-explanation-text-for-permission-prompts","heading":"Permission prompts can explain why auto mode is not skipping them","tier":"notice","area":"Auto Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/auto-mode-off-explanation-text-for-permission-prompts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Permission prompts can explain why auto mode is not skipping them\n\nNew messages explain that an action is allowed but Claude still asks, because auto mode is unavailable, and say why\n\n**Unclear.** It is not clear when or where these messages appear.\n\n**What**\n\nAuto mode is a permission mode in which Claude Code approves actions without asking you. Claude Code now has messages saying that an action is allowed but Claude is still asking you, because auto mode is unavailable. The message gives one of these reasons:\n\n- Your organization has turned auto mode off.\n\n- Managed settings (settings set by an administrator) turn it off.\n\n- The `disableAutoMode` setting turns it off.\n\n- The current model does not support it. The message suggests `\/model` to switch model.\n\n- Fast mode is on. The message suggests running `\/fast off`.\n\n- Auto mode is unavailable for some other reason.\n\n**Why**\n\nThe messages tell you why you are still being asked for permission and, where possible, what you can change to stop it.\n\n- Area: Auto Mode\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}