{"version":"2.1.300","anchor":"bridge-sandbox-option-no-longer-defaults-to-false","canonical_anchor":"bridge-sandbox-option-no-longer-defaults-to-false","heading":"Remote sessions no longer force sandbox off when it is not set","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/bridge-sandbox-option-no-longer-defaults-to-false","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Remote sessions no longer force sandbox off when it is not set\n\nIn Remote Control start-up settings, leaving `sandbox` unset no longer means off, so another default can apply\n\n**Unclear.** Which default applies when `sandbox` is left unset is not stated.\n\n**What**\n\nA sandbox is a restricted space that limits what commands Claude Code runs can touch. When a session is started through the bridge used by Remote Control, its start-up settings include a `sandbox` option.\n\nBefore, leaving `sandbox` unset was the same as setting it to false. Now an unset `sandbox` stays unset, so Claude Code can tell \"not chosen\" apart from \"turned off\".\n\n**Why**\n\nA session that does not say anything about the sandbox can now pick up a different default instead of having it forced off.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}