{"version":"2.1.234","anchor":"sandbox-exclusion-list-stops-being-an-escape-hatch-once-unsa","canonical_anchor":"sandbox-exclusion-list-stops-being-an-escape-hatch-once-unsa","heading":"Sandbox exclusion list stops being an escape hatch once unsandboxed commands are disabled","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/sandbox-exclusion-list-stops-being-an-escape-hatch-once-unsa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Sandbox exclusion list stops being an escape hatch once unsandboxed commands are disabled\n\nYour sandbox exclusion list stops working as a bypass once unsandboxed commands are disabled.\n\n**What**\n\nA command listed in `sandbox.excludedCommands` used to run outside the sandbox on the strength of that list alone. It now also requires that unsandboxed commands have not been disabled for the session, so once something turns them off the exclusion list no longer opens a hole.\n\n**Evidence**\n\n`unsandboxedCommandsDisabled`\n\n- Area: Sandbox\n- Names: `sandbox.excludedCommands`\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}