{"version":"2.1.234","anchor":"the-remote-kill-switch-for-bypasspermissions-mode-is-gone","canonical_anchor":"the-remote-kill-switch-for-bypasspermissions-mode-is-gone","heading":"The remote kill switch for bypassPermissions mode is gone","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/the-remote-kill-switch-for-bypasspermissions-mode-is-gone","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### The remote kill switch for bypassPermissions mode is gone\n\nA remote switch can no longer force you out of bypassPermissions mode mid-session; only the admin setting does.\n\n**What**\n\nv2.1.233 had a startup check that consulted a remote flag once per process and, if it fired, forced the session out of bypassPermissions back to the default mode and marked the mode unavailable. That check and its one-shot latch are removed. The `disableBypassPermissionsMode` admin setting still parses and still blocks the mode.\n\n**Details**\n\n- The removed flag name no longer appears anywhere in the build, and the latch class retains only its auto-mode half.\n\n**Evidence**\n\n`disableBypassPermissionsMode`\n\n- Area: Permissions\n- Names: `disableBypassPermissionsMode`\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 4\/5"}