{"version":"2.1.317","anchor":"sandbox-new-windows-error-for-too-long-commands-with-added","canonical_anchor":"sandbox-new-windows-error-for-too-long-commands-with-added","heading":"Clearer error on Windows when a sandboxed command gets too long","tier":"notice","area":"Windows","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/sandbox-new-windows-error-for-too-long-commands-with-added","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Clearer error on Windows when a sandboxed command gets too long\n\nOn Windows, a sandboxed command made too long by folders added later now gets its own error with suggested fixes\n\n**What**\n\nThe sandbox is a protected space that limits what commands Claude runs can touch. On Windows, a command has a maximum length. Folders added after the sandbox started, from worktrees (separate working copies of a project) or from `\/add-dir`, add file rules to every command and can push it over that limit.\n\nBefore, this produced only a general \"too long\" message. Now Claude Code says \"Command is too long to run in the Windows sandbox.\" and suggests:\n\n- writing the command to a file and running that\n\n- running fewer subagents (helper agents) at once\n\n- restarting\n\n**Why**\n\nWindows sandbox users with many worktrees or added folders now get an explanation for a failure that was confusing before.\n\n- Area: Windows\n- Names: `\/add-dir`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}