{"version":"2.1.280","anchor":"cli-now-prints-an-explicit-stop-notice-before-a-generic-exe","canonical_anchor":"cli-now-prints-an-explicit-stop-notice-before-a-generic-exe","heading":"CLI now prints an explicit stop notice before a generic 'Execution error'","tier":"notice","area":"CLI","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/cli-now-prints-an-explicit-stop-notice-before-a-generic-exe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### CLI now prints an explicit stop notice before a generic 'Execution error'\n\nClaude Code now prints a specific stop notice before the generic 'Execution error' message\n\n**Unclear.** The finding does not say what triggers the 'automatic mode unavailable' condition or what 'auto mode' refers to.\n\n**What**\n\nWhen a command fails with the `error_during_execution` result, the CLI now prints an extra line to stderr (the terminal's error output) before the existing generic 'Execution error' message, if one was recorded. This new line explains that automatic mode is unavailable.\n\n**Why**\n\nPreviously a failure in this case only showed the generic 'Execution error' text, giving no clue as to the specific cause. The added notice gives a more specific reason for the stop, making it easier to understand why execution halted.\n\n- Area: CLI\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}