{"version":"2.1.317","anchor":"windows-sandbox-argv-limit-error-mapped-when-denies-were-add","canonical_anchor":"windows-sandbox-argv-limit-error-mapped-when-denies-were-add","heading":"Clearer error on Windows when a sandboxed command is too long","tier":"notice","area":"Windows","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/windows-sandbox-argv-limit-error-mapped-when-denies-were-add","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Clearer error on Windows when a sandboxed command is too long\n\nOn Windows, a command that is too long for the sandbox now gets a clearer error, worded for whether added deny rules or the command caused it\n\n**What**\n\nOn Windows, Claude Code can run commands inside a sandbox, a fenced-off space that limits what a command can reach. Windows limits how long a command line can be. When that limit is hit, Claude Code no longer passes the raw Windows error back as it is. It now turns it into a clearer error, and the error depends on the cause:\n\n- Claude Code added its own deny rules (rules that block access) to the command, and those made it too long.\n\n- The command itself is too long.\n\n**Why**\n\nWindows users get an error that explains the problem instead of a raw system message.\n\n- Area: Windows\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}