{"version":"2.1.280","anchor":"stoperror-parsing-now-distinguishes-a-stopped-reason","canonical_anchor":"stoperror-parsing-now-distinguishes-a-stopped-reason","heading":"Stop\/error parsing now distinguishes a 'stopped' reason","tier":"internal","area":"Error Handling","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/stoperror-parsing-now-distinguishes-a-stopped-reason","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Stop\/error parsing now distinguishes a 'stopped' reason\n\nInternal error parsing now separately flags when a run was stopped\n\n**Unclear.** The finding doesn't say what consumes the new `stopped` field or how it changes visible behavior.\n\n**What**\n\nA helper that extracts error information from JSON responses used to return just the error text. It now also checks a 'reason' field in the response and returns whether the run was specifically stopped, alongside the error.\n\n**Why**\n\nThis lets Claude Code's internal handling distinguish a run that was deliberately stopped from other kinds of failures, which can affect how the situation is reported or recovered from.\n\n- Area: Error Handling\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}