A remote switch can no longer force you out of bypassPermissions mode mid-session; only the admin setting does.
What's wrong with this entry?
v2.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.
- The removed flag name no longer appears anywhere in the build, and the latch class retains only its auto-mode half.
disableBypassPermissionsMode
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.225
VS Code-owned sessions get their own settings defaultMode handling
Both mention bypass mode
-
v2.1.223
Permission circuit breakers now have a capability table
Both mention bypass
-
v2.1.227
Auto-mode guidance reminders now also appear in bypassPermissions
Both mention bypass