{"version":"2.1.285","anchor":"sandbox-failifunavailable-can-also-be-forced-by-another-cond","canonical_anchor":"sandbox-failifunavailable-can-also-be-forced-by-another-cond","heading":"Claude Code can refuse to run without the sandbox in more cases","tier":"notice","area":"Sandbox","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/sandbox-failifunavailable-can-also-be-forced-by-another-cond","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Claude Code can refuse to run without the sandbox in more cases\n\nRefusing to run when the sandbox is unavailable can now be triggered by another condition as well as `sandbox.failIfUnavailable`\n\n**Unclear.** What the added condition checks is not settled.\n\n**What**\n\nThe sandbox limits which files and network addresses commands run by Claude can reach. Claude Code decides whether to refuse to start when the sandbox cannot run. Before, only the `sandbox.failIfUnavailable` setting decided this, and it was off unless you set it. Now a second condition can also make Claude Code refuse.\n\n**Why**\n\nClaude Code may now refuse to run without the sandbox in some setups, even if you have not set `sandbox.failIfUnavailable`.\n\n- Area: Sandbox\n- Names: `sandbox.failIfUnavailable`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}