{"version":"2.1.314","anchor":"auto-mode-unavailable-message-now-has-distinct-reasons-incl","canonical_anchor":"auto-mode-unavailable-message-now-has-distinct-reasons-incl","heading":"Auto mode explains more specifically why it cannot check actions","tier":"notice","area":"Auto Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/auto-mode-unavailable-message-now-has-distinct-reasons-incl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Auto mode explains more specifically why it cannot check actions\n\nWhen auto mode cannot check actions, Claude Code now gives a specific reason and fix, including when `CLAUDE_CODE_AUTO_MODE_SERVER` turns the check off\n\n**What**\n\nAuto mode is a permission mode where Claude Code checks each action and decides whether it can go ahead without asking you. When that check is unavailable, Claude Code shows a message explaining why. The message now picks from a wider set of reasons, and each one has its own explanation and suggested fix.\n\nBefore, the message only told apart three situations: experimental betas turned off, the check switched off, and the check not offered. The new reasons are:\n\n- The `CLAUDE_CODE_AUTO_MODE_SERVER` environment variable has turned the server check off. The message says Claude Code no longer has a check of its own to use instead, and tells you to set `CLAUDE_CODE_AUTO_MODE_SERVER` to `1` or remove it to use auto mode.\n\n- The feature is not covered.\n\n- The check was not requested.\n\n**Why**\n\nIf auto mode falls back and stops working for you, the message now points to the specific cause and what to change, instead of a more general explanation.\n\n- Area: Auto Mode\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}