{"version":"2.1.323","anchor":"bash-sandbox-refusal-passed-to-model-as-a-note","canonical_anchor":"bash-sandbox-refusal-passed-to-model-as-a-note","heading":"Sandbox refusals are passed to Claude as a note meant for you","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/bash-sandbox-refusal-passed-to-model-as-a-note","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Sandbox refusals are passed to Claude as a note meant for you\n\nWhen the sandbox refuses a command, Claude now sees the refusal marked as a note for the user, not for Claude to act on\n\n**What**\n\nThe sandbox is the protected area Claude Code can run shell commands in, limiting what they can reach. When a command result carries a sandbox refusal, Claude Code now hands it to Claude prefixed with \"For the user, not for you to act on:\" and then the refusal text.\n\n**Why**\n\nClaude can see that the sandbox refused something, but is told to leave the decision to you rather than try to work around it.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}