{"version":"2.1.307","anchor":"sandbox-violations-and-sandboxed-status-returned-from-bash","canonical_anchor":"sandbox-violations-and-sandboxed-status-returned-from-bash","heading":"Shell results now report sandbox violations and whether the sandbox was used","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/sandbox-violations-and-sandboxed-status-returned-from-bash","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Shell results now report sandbox violations and whether the sandbox was used\n\nBash and PowerShell results now say whether a command ran in the sandbox and list any sandbox violations\n\n**What**\n\nThe sandbox is a restricted environment that limits what commands run by Claude can touch. Results from the Bash and PowerShell tools, which run shell commands, now include:\n\n- whether the command ran in the sandbox\n\n- any sandbox violations, meaning actions the sandbox blocked\n\nThere are also smaller changes:\n\n- In PowerShell, a failed attempt to change the working folder now shows the notice that the folder was reset.\n\n- The sandbox check that runs before a command starts now has a time limit.\n\n**Why**\n\nBoth Claude and the interface can now see when the sandbox blocked something a command tried to do.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}