{"version":"2.1.300","anchor":"claude-code-force-sandbox-removed-from-env-allowlist-and-bri","canonical_anchor":"claude-code-force-sandbox-removed-from-env-allowlist-and-bri","heading":"CLAUDE_CODE_FORCE_SANDBOX no longer exists","tier":"notice","area":"Sandbox","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/claude-code-force-sandbox-removed-from-env-allowlist-and-bri","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### `CLAUDE_CODE_FORCE_SANDBOX` no longer exists\n\nThe `CLAUDE_CODE_FORCE_SANDBOX` environment variable has been removed, and remote bridge setup no longer passes a sandbox option\n\n**Unclear.** It is not shown whether the sandbox can now be forced some other way.\n\n**What**\n\nThe environment variable `CLAUDE_CODE_FORCE_SANDBOX` is gone from Claude Code. A sandbox is a restricted space that limits what commands Claude runs can touch. Setting this variable no longer has any effect, because Claude Code no longer looks for it.\n\nSeparately, when Claude Code sets up a remote bridge (the link that lets a session be driven from somewhere else), it no longer passes a sandbox option along.\n\n**Why**\n\nIf you relied on `CLAUDE_CODE_FORCE_SANDBOX` to make sure the sandbox was always used, that switch no longer does anything.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}