{"version":"2.1.285","anchor":"disablenosandbox-check-gains-an-early-true-path","canonical_anchor":"disablenosandbox-check-gains-an-early-true-path","heading":"The sandbox check for disableNoSandbox gains an extra condition","tier":"internal","area":"Sandbox","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/disablenosandbox-check-gains-an-early-true-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### The sandbox check for `disableNoSandbox` gains an extra condition\n\nA sandbox check can now pass on a new condition before it looks at the `disableNoSandbox` setting\n\n**Unclear.** What the new condition tests, and what passing this check allows, are not clear.\n\n**What**\n\nThe sandbox is a restricted area Claude Code can run commands in. One of its checks used to start by looking at the `disableNoSandbox` setting and failing if it was not set. It now first tests a new condition and passes straight away if that condition holds. Only after that does it look at `disableNoSandbox`, the `IS_SANDBOX` environment variable and bubblewrap (a Linux tool used for sandboxing).\n\n**Why**\n\nThis could change when Claude Code allows running without a sandbox.\n\n- Area: Sandbox\n- Names: `disableNoSandbox`, `IS_SANDBOX`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}