{"version":"2.1.248","anchor":"notice-when-the-command-sandbox-is-turned-off-mid-session","canonical_anchor":"notice-when-the-command-sandbox-is-turned-off-mid-session","heading":"Notice when the command sandbox is turned off mid-session","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/notice-when-the-command-sandbox-is-turned-off-mid-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Notice when the command sandbox is turned off mid-session\n\nTurning off sandboxing mid-session now tells Claude the old restrictions no longer apply.\n\n**What**\n\nWhen sandboxing is disabled, the model is now told directly that commands run without sandbox restrictions and that earlier sandbox instructions no longer apply, so it does not keep working around limits that are gone.\n\n**Details**\n\n- Two new lists of refusal reasons ship alongside it: write refusals (`compliance_restricted`, `org_mismatch`, `org_toggle_disabled`, `summon_foreign_sender`, `user_entitlement_denied`, `write_gate_disabled`) and device-binding refusals (`bind_attestation_stale`, `bound_session_unattested_write`, `untrusted_device`).\n\n**Evidence**\n\n`Commands now run without sandbox restrictions; the earlier sandbox instructions no longer apply.`\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}