{"version":"2.1.280","anchor":"new-classifier-for-retryable-automode-failure-reasons","canonical_anchor":"new-classifier-for-retryable-automode-failure-reasons","heading":"New classifier for retryable automode failure reasons","tier":"internal","area":"Auto Mode","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-classifier-for-retryable-automode-failure-reasons","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New classifier for retryable automode failure reasons\n\nAutomode now groups blocked, unavailable, and parsing-error failures as one retryable category\n\n**Unclear.** The finding does not say what consuming code does with this classification, such as whether it actually triggers a retry.\n\n**What**\n\nA new internal function now classifies certain automode failure reasons as belonging to one group: `automode-blocked`, `automode-unavailable`, and `automode-parsing-error` are all treated as the same category, distinct from other outcomes like `user-rejected`, `permission-rule`, `interrupted`, and `cancelled`.\n\n**Why**\n\nGrouping these reasons together lets Claude Code treat them consistently, for example when deciding whether a failed automode attempt is worth retrying, rather than handling each reason as a one-off case.\n\n- Area: Auto Mode\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}