{"version":"2.1.280","anchor":"e2big-shell-exec-failures-now-classified-distinctly","canonical_anchor":"e2big-shell-exec-failures-now-classified-distinctly","heading":"Argument-list-too-long (E2BIG) bash spawn failures get a distinct error code","tier":"internal","area":"Bash Tool","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/e2big-shell-exec-failures-now-classified-distinctly","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Argument-list-too-long (E2BIG) bash spawn failures get a distinct error code\n\nBash commands that fail to start because the argument list is too long are now tagged as spawn_arg_limit instead of a generic error\n\n**What**\n\n- A failed bash-tool spawn now carries an optional `preSpawnErrorCode` alongside the existing `preSpawnError` message.\n\n- When that code is `e2big` (the operating-system error for \"argument list too long\"), the error is now tagged with `{ kind: \"spawn_arg_limit\" }` via a wrapper, instead of throwing a generic pre-spawn error.\n\n- This applies both to the general pre-spawn failure path and to a monitor's pre-spawn step.\n\n**Why** Distinguishing this specific failure lets Claude Code (and anyone building on it) recognize when a command failed simply because its arguments were too long to pass to the operating system, rather than treating it the same as any other spawn failure.\n\n- Area: Bash Tool\n- Names: `e2big`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}