{"version":"2.1.314","anchor":"sandbox-failure-analysis-of-denied-paths-and-symptoms","canonical_anchor":"sandbox-failure-analysis-of-denied-paths-and-symptoms","heading":"Claude Code now sorts out why a sandboxed Bash command failed","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/sandbox-failure-analysis-of-denied-paths-and-symptoms","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Claude Code now sorts out why a sandboxed Bash command failed\n\nWhen a sandboxed Bash command fails, Claude Code now classifies the cause and notes which blocked file paths the command touched\n\n**What**\n\nA sandbox is a restricted environment that limits which files and system features a command can use. When Claude runs a Bash command in the sandbox, Claude Code now examines the result and sorts any failure into kinds, such as:\n\n- operation not permitted\n\n- read-only file system\n\n- blocked macOS app launching (Launch Services)\n\n- sandbox unavailable\n\nIt also notes which file paths the sandbox blocks from being read were mentioned by the command or appeared in its output.\n\n**Why**\n\nThis looks like diagnostics for sandbox denials. In practice, Claude Code can now tell which kind of sandbox restriction got in a command's way.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}