{"version":"2.1.280","anchor":"new-auto-mode-failureblocking-messages-tied-to-a-safety-ver","canonical_anchor":"new-auto-mode-failureblocking-messages-tied-to-a-safety-ver","heading":"New auto mode failure\/blocking messages tied to a safety verdict system","tier":"notice","area":"Auto Mode","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-auto-mode-failureblocking-messages-tied-to-a-safety-ver","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New auto mode failure\/blocking messages tied to a safety verdict system\n\nAuto mode now has messages for when it can't get a safety verdict and gives up or blocks an action\n\n**Unclear.** The finding does not say what triggers a missing safety verdict or what user-facing experience (e.g. UI, logs) surfaces these messages.\n\n**What**\n\nClaude Code's 'auto mode' has two new failure messages tied to a safety verdict system, which checks whether an action is safe before auto mode proceeds:\n\n- One message appears when auto mode stops after repeatedly responding without ever producing a safety verdict, marking it as unavailable ('automode-unavailable') and recording this as the reason an agent got blocked.\n\n- The other message appears when auto mode is unable to evaluate an action at all, so it blocks the action rather than allow something unchecked.\n\n**Why**\n\nThese messages make it clear to the user when auto mode has stopped working or blocked something because it couldn't confirm an action was safe, rather than failing silently or without explanation.\n\n- Area: Auto Mode\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}