{"version":"2.1.309","anchor":"shell-exec-stricter-cwd-loss-sandbox-wrap-and-disk-full-ha","canonical_anchor":"shell-exec-stricter-cwd-loss-sandbox-wrap-and-disk-full-ha","heading":"Shell commands are refused when their folder is gone or the sandbox fails","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/shell-exec-stricter-cwd-loss-sandbox-wrap-and-disk-full-ha","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Shell commands are refused when their folder is gone or the sandbox fails\n\nCommands now refuse to run if their working folder is gone or the Windows sandbox did nothing, and disk-full errors say more\n\n**What**\n\nClaude Code is now stricter about when it runs a shell command, and says more when something fails:\n\n- If the folder a command should run in has been deleted, moved, replaced by a link or cannot be read, the command is not run, and you are told to re-issue it if it still makes sense where the session is now.\n\n- On Windows, if the sandbox (the restricted environment that limits what a command can touch) placed no restrictions on a command, the command is not run.\n\n- Disk-full errors now say when your disk quota is used up, and name the temporary-files drive that is full.\n\n**Why**\n\nWhen the sandbox or the working folder breaks, Claude Code now stops instead of running the command anyway, so a command never runs unrestricted or in the wrong place without you knowing.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}