{"version":"2.1.248","anchor":"claude-code-can-refuse-to-start-when-the-sandbox-is-unavaila","canonical_anchor":"claude-code-can-refuse-to-start-when-the-sandbox-is-unavaila","heading":"Claude Code can refuse to start when the sandbox is unavailable","tier":"use","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/claude-code-can-refuse-to-start-when-the-sandbox-is-unavaila","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Claude Code can refuse to start when the sandbox is unavailable\n\nSet sandbox.failIfUnavailable to make Claude Code exit instead of running without a sandbox.\n\n**What**\n\nSandbox startup moved into its own step that can decline to launch. If the setting `sandbox.failIfUnavailable` is on and no working sandbox is found, Claude Code writes an error to stderr and exits with code 1. The setting defaults to false, in which case it logs a warning and records one setup issue instead. Remote sessions skip the check entirely.\n\n**Details**\n\n- The setting is marked restrictive in the settings schema, so it can be enforced from a managed settings file.\n- When startup is refused, the remaining session startup steps are skipped.\n\n**Evidence**\n\n`sandbox.failIfUnavailable is set \u2014 refusing to start without a working sandbox.`\n\n- Area: Sandbox\n- Names: `sandbox.failIfUnavailable`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}