What
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.
Details
- The removed flag name no longer appears anywhere in the build, and the latch class retains only its auto-mode half.
Evidence
disableBypassPermissionsMode
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundledisableBypassPermissionsMode
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up disableBypassPermissionsMode, on All settings.
| Locks | Applies the strictest value any source sets. When no source sets a strict value, applies a looser value only from the highest source | [`allowManagedPermissionRulesOnly`](#allowmanagedpermissionrulesonly), [`permissions.disableBy…settings-reference see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up disableBypassPermissionsMode, on All settings.