{"version":"2.1.314","anchor":"new-startup-refusal-reason-sandbox-required-unavailable","canonical_anchor":"new-startup-refusal-reason-sandbox-required-unavailable","heading":"Startup can fail with a distinct reason when a required sandbox cannot run","tier":"notice","area":"Sandbox","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/new-startup-refusal-reason-sandbox-required-unavailable","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Startup can fail with a distinct reason when a required sandbox cannot run\n\nClaude Code adds a startup refusal reason for when a sandbox is required but cannot run, such as bubblewrap missing\n\n**Unclear.** It is not clear whether Claude Code reports this reason yet or what triggers it.\n\n**What**\n\nClaude Code has a list of reasons it can give for refusing to start. A new one, `sandbox_required_unavailable`, means a working sandbox is required but cannot run in this session. A sandbox is a protected space that limits what commands can reach. Examples are bubblewrap, the Linux sandboxing program, being missing, or the platform not being supported.\n\n**Why**\n\nPrograms that start Claude Code under a policy that requires a sandbox get a clear, machine-readable reason, so they can offer a fix instead of just retrying.\n\n- Area: Sandbox\n- Names: `sandbox_required_unavailable`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: no"}