{"version":"2.1.247","anchor":"sandbox-status-can-be-reported-as-machine-readable-json","canonical_anchor":"sandbox-status-can-be-reported-as-machine-readable-json","heading":"Sandbox status can be reported as machine-readable JSON","tier":"use","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/sandbox-status-can-be-reported-as-machine-readable-json","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Sandbox status can be reported as machine-readable JSON\n\nSandbox status can be emitted as a JSON object covering availability, enablement, strict mode and filesystem policy.\n\n**What**\n\nA new sandbox status path emits a JSON object stamped `statusVersion: 2` covering whether sandboxing is available, installed, policy-locked and supported, whether it is enabled, whether strict mode is on, and the filesystem policy, with reasons attached.\n\n**Details**\n\n- Two provenance fields say where the settings came from: one for enablement and one for strict mode, each reported as `forced`, `policy`, `settings` or `off`.\n- Nothing carrying a status version existed in the previous build.\n- Which command surfaces this output is not wired up anywhere visible in the bundle.\n\n**Evidence**\n\n`strictModeSource`\n\n- Area: Sandbox\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}