{"version":"2.1.318","anchor":"auto-mode-classifier-unavailable-now-falls-back-to-the-quest","canonical_anchor":"auto-mode-classifier-unavailable-now-falls-back-to-the-quest","heading":"Auto mode now asks you more often when its safety check is unavailable","tier":"notice","area":"Auto Mode","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/auto-mode-classifier-unavailable-now-falls-back-to-the-quest","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Auto mode now asks you more often when its safety check is unavailable\n\nWhen auto mode's safety check is down, any action that can show a dialog now falls back to asking you, not only Claude's own questions\n\n**What**\n\nAuto mode lets Claude act without asking each time, using a classifier, a separate check that decides whether each action is safe. When that check is unavailable, Claude Code falls back to showing you a question dialog. That used to happen only for `AskUserQuestion`, the tool Claude uses to ask you something. It now happens for any action that can show a dialog. The message now reads \"Auto mode classifier unavailable, falling back to the question dialog\".\n\nThere is also a new refusal for some scripted calls, with the reason \"Refused: auto mode's check of Claude's code doesn't cover this call\".\n\n**Why**\n\nWhen the check is down, you are more often asked to decide instead of having the action refused outright.\n\n- Area: Auto Mode\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}