What
The remote flag that could disable bypassPermissions mode, the asynchronous re-check that exited the process mid-session, and the "disabled by your organization policy" message are all removed. The only remaining route to disabling the mode is the disableBypassPermissionsMode setting.
Evidence
Bypass permissions mode was disabled by settings
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.