{"version":"2.1.314","anchor":"auto-mode-classifier-tracks-stage-1-allows-that-fail-strict","canonical_anchor":"auto-mode-classifier-tracks-stage-1-allows-that-fail-strict","heading":"Auto mode no longer accepts a first-stage approval that ended badly","tier":"notice","area":"Auto Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/auto-mode-classifier-tracks-stage-1-allows-that-fail-strict","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Auto mode no longer accepts a first-stage approval that ended badly\n\nAuto mode's safety checker now sets aside a first-stage approval unless the reply ended cleanly and in the expected form\n\n**Unclear.** Whether this stricter check is switched on in released builds is not clear.\n\n**What**\n\nAuto mode lets Claude carry out actions without asking you each time. A checker decides whether each action is safe, and it works in two stages. Before, an approval from the first stage was accepted as it stood.\n\nNow a first-stage approval is set aside unless both of these hold:\n\n- The checker's reply finished normally rather than being cut off.\n\n- The reply has the expected well-formed answer.\n\nAn approval that fails either test is treated as unreadable. The action then goes on to the second stage, or the check fails.\n\n**Why**\n\nA cut-off or malformed approval from the checker can no longer let an action through auto mode without anyone noticing.\n\n- Area: Auto Mode\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}