{"version":"2.1.307","anchor":"sandbox-violation-fields-on-tool-results","canonical_anchor":"sandbox-violation-fields-on-tool-results","heading":"Tool results now carry sandbox information","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/sandbox-violation-fields-on-tool-results","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Tool results now carry sandbox information\n\nTool results now include whether the action ran in the sandbox and any sandbox rule it broke\n\n**What**\n\nThe sandbox is a restricted space Claude Code can run commands in, limiting what they may touch. When a tool finishes, its result now includes whether it ran inside the sandbox and any sandbox violations, meaning things it tried to do that the sandbox blocked. This goes into the message Claude reads.\n\n**Why**\n\nClaude may now be told when an action ran into the sandbox's limits.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}