{"version":"2.1.277","anchor":"cli-budgettask-budget-argument-errors-now-thrown-as-a-diffe","canonical_anchor":"cli-budgettask-budget-argument-errors-now-thrown-as-a-diffe","heading":"CLI budget\/task-budget argument errors now thrown as a different error class","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/cli-budgettask-budget-argument-errors-now-thrown-as-a-diffe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### CLI budget\/task-budget argument errors now thrown as a different error class\n\nErrors for invalid --max-budget-usd or --task-budget values now use a different internal error class, same message\n\n**What**\n\nWhen you pass an invalid value to `--max-budget-usd` or `--task-budget` (for example, a non-positive number), Claude Code still reports the same error text, but now throws it as a different internal error class.\n\n**Why**\n\nThis is an internal change to error handling and shouldn't be noticeable in normal use; the error message you see stays the same.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}