{"version":"2.1.319","anchor":"bash-command-wrapping-can-refuse-commands-too-long-for-windo","canonical_anchor":"bash-command-wrapping-can-refuse-commands-too-long-for-windo","heading":"Bash commands too long for Windows are now refused instead of run","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/bash-command-wrapping-can-refuse-commands-too-long-for-windo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Bash commands too long for Windows are now refused instead of run\n\nWhen a shell command would be too long for Windows, Claude Code now swaps it for a command that exits with code 126 and reports why\n\n**What**\n\nWhen Claude runs a shell command, Claude Code builds the full command line before running it. It now checks whether that command line would be too long for Windows. If it would be, Claude Code does not run it. It runs `\\builtin exit 126` instead, which stops straight away with exit code 126, and reports one of these reasons:\n\n- `shell_prefix`\n\n- `credential_scrub`\n\n- `startup_files`\n\n- `too_long`\n\nBefore, the command line was put together and run with no length check.\n\n**Why**\n\nVery long commands now fail with a clear exit code and a reason rather than being passed on as they are.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}