{"version":"2.1.293","anchor":"sandbox-policy-callback-made-constant-false","canonical_anchor":"sandbox-policy-callback-made-constant-false","heading":"A sandbox-related check now always answers no","tier":"internal","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/sandbox-policy-callback-made-constant-false","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### A sandbox-related check now always answers no\n\nAn internal check tied to the sandbox no longer looks at any conditions and always returns false\n\n**Unclear.** What this check controls, and so what changes for a user, is not known.\n\n**What**\n\nA sandbox is a walled-off area that limits what commands can reach on your computer. An internal check related to it used to look at two conditions before answering. It now always answers no.\n\n**Why**\n\nThe answer no longer depends on a feature check, so whatever it governs behaves the same way every time.\n\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}