{"version":"2.1.280","anchor":"bash-tool-now-reports-a-sandbox-violation-remedy-on-tool-r","canonical_anchor":"bash-tool-now-reports-a-sandbox-violation-remedy-on-tool-r","heading":"Bash tool now reports a 'sandbox_violation' remedy on tool results","tier":"notice","area":"Sandbox","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/bash-tool-now-reports-a-sandbox-violation-remedy-on-tool-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Bash tool now reports a 'sandbox_violation' remedy on tool results\n\nBash tool results now flag a sandbox_violation remedy when a sandboxed command's stderr shows a sandbox violation\n\n**What**\n\nWhen a Bash command runs inside a sandbox (an isolated environment that restricts what a command can do, such as file or network access) and the sandbox notes that the command tried to do something it blocked, the tool result now includes an extra field: `remedy: { kind: \"sandbox_violation\" }`. This only appears when the command actually finished running rather than being interrupted.\n\n**Why**\n\nThis surfaces sandbox restriction problems directly in the tool result instead of leaving them buried in stderr text, making it easier to notice when a command failed because of sandboxing rather than a genuine error in the command itself.\n\n- Area: Sandbox\n- Names: `sandbox_violation`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}