{"version":"2.1.323","anchor":"sandbox-required-startup-error-message-reworded","canonical_anchor":"sandbox-required-startup-error-message-reworded","heading":"Shorter message when Claude Code refuses to start without a working sandbox","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/sandbox-required-startup-error-message-reworded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Shorter message when Claude Code refuses to start without a working sandbox\n\nThe refusal to start without a working sandbox is now one line pointing to `sandbox.failIfUnavailable`\n\n**What**\n\nThe sandbox is a fenced-off area where Claude Code runs commands with limits on what they can touch. If you set `sandbox.failIfUnavailable` and the sandbox cannot run, Claude Code refuses to start. Its message now reads \"Refusing to start without a working sandbox (see sandbox.failIfUnavailable).\" The separate line saying that `sandbox.failIfUnavailable` is set has been removed.\n\n**Why**\n\nOnly the wording changed. Claude Code still refuses to start in the same cases.\n\n- Area: Sandbox\n- Names: `sandbox.failIfUnavailable`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}