{"version":"2.1.314","anchor":"sandbox-notes-for-tool-results-rewritten","canonical_anchor":"sandbox-notes-for-tool-results-rewritten","heading":"Claude gets clearer guidance when the sandbox blocks something","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/sandbox-notes-for-tool-results-rewritten","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Claude gets clearer guidance when the sandbox blocks something\n\nWhen the sandbox blocks a command, Claude is now told that rerunning will fail the same way and to report the block to you\n\n**What**\n\nThe sandbox is a walled-off space that limits what the commands Claude runs can touch. Claude Code now writes guidance for Claude about sandbox blocks, covering:\n\n- files or folders that look missing or empty because access was denied\n\n- a LaunchServices error\n\n- a sandbox that could not start\n\nThe guidance says that running the same thing again will fail the same way, and tells Claude to report the block to you rather than use another file in place of the blocked one.\n\n**Why**\n\nClaude is steered away from working around a sandbox block and toward telling you about it.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}