[DOCS] VS Code docs missing permission-picker behavior when `disableBypassPermissionsMode` is set

Open 💬 5 comments Opened Mar 5, 2026 by coygeek

Documentation Type

Unclear/confusing documentation

Documentation Location

https://code.claude.com/docs/en/vs-code

Section/Topic

Permission mode picker behavior under managed/policy settings.

Current Documentation

VS Code docs currently describe permission modes generally:

Permission modes: click the mode indicator at the bottom of the prompt box to switch modes...

Settings docs also define the policy control:

disableBypassPermissionsMode | Set to "disable" to prevent bypassPermissions mode from being activated.

What's Wrong or Missing?

Changelog v2.1.69 states that the VS Code picker now respects permissions.disableBypassPermissionsMode by hiding bypass mode when set to disable.

This VS Code-specific picker behavior is not documented on the VS Code page, leaving policy-managed users uncertain about why the mode is unavailable.

Suggested Improvement

Add a note in the VS Code permission mode section that:

  • The picker reflects effective policy/managed settings
  • disableBypassPermissionsMode: "disable" hides bypass mode
  • This behavior applies to managed and policy settings

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/vs-code | Permission mode picker behavior should be documented here |
| https://code.claude.com/docs/en/settings | Defines disableBypassPermissionsMode policy setting |
| https://code.claude.com/docs/en/permissions | Managed-permission policy semantics referenced by VS Code behavior |

Total scope: 3 pages affected

Source: Changelog v2.1.69

Exact changelog entry:

[VSCode] The permission mode picker now respects permissions.disableBypassPermissionsMode from your effective Claude Code settings (including managed/policy settings) — when set to disable, bypass permissions mode is hidden from the picker

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗