{"version":"2.1.315","anchor":"auto-mode-stop-notices-attached-to-error-results","canonical_anchor":"auto-mode-stop-notices-attached-to-error-results","heading":"Runs that end in an error now keep a note about auto mode stopping","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/auto-mode-stop-notices-attached-to-error-results","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Runs that end in an error now keep a note about auto mode stopping\n\nWhen a run ends with an error during execution, Claude Code now works out an auto mode stop notice and keeps it with that result\n\n**Unclear.** It is not clear whether, or where, these stop notices are shown to you.\n\n**What**\n\nWhen a run ends with an error while it was executing, Claude Code now works out a stop notice for auto mode and keeps it attached to that result. Auto mode is the mode in which Claude Code carries on with less asking. Claude Code's internal usage reporting also now takes the reason a run ended from the new result when deciding whether it was terminated.\n\n**Why**\n\nThis could let Claude Code later tell you why auto mode stopped when a run fails.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}