claude-code - 💡(How to fix) Fix [DOCS] VS Code auto mode docs still tie mode-picker visibility to bypass-permissions setting

Documentation Type

Incorrect/outdated documentation

Documentation Location

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

Section/Topic

Extension settings and VS Code permission mode picker behavior for Auto mode

Current Documentation

The VS Code extension settings table currently says:

allowDangerouslySkipPermissions | false | Adds Auto mode and Bypass permissions to the mode selector. Auto mode has plan, admin, model, and provider requirements, so it may remain unavailable even with this toggle on. Use Bypass permissions only in sandboxes with no internet access.

The permission modes page also says:

Auto mode appears in the mode indicator after you enable Allow dangerously skip permissions in the extension settings, but it stays unavailable until your account meets every requirement listed in the auto mode section.

Neither page documents the first-time notice shown on the VS Code new-session screen when Auto mode is active.

What's Wrong or Missing?

Claude Code v2.1.154 changed VS Code Auto mode behavior: Auto mode no longer requires the bypass-permissions setting to appear in the mode picker, and the new-session screen shows a dismissable notice explaining Auto mode the first time it is active.

A. The VS Code settings table is outdated

The allowDangerouslySkipPermissions row still says this setting adds both Auto mode and Bypass permissions to the mode selector. That makes Auto mode sound coupled to a dangerous bypass-permissions toggle, even though the v2.1.154 release note says Auto mode no longer requires that setting to appear.

B. The permission modes page repeats the outdated VS Code condition

The VS Code tab on the permission modes page says Auto mode appears only after enabling Allow dangerously skip permissions. That is now misleading for users whose account meets Auto mode requirements but who have not enabled the bypass-permissions setting.

C. The first-time new-session notice is undocumented

The release note also says VS Code shows a dismissable notice on the new-session screen explaining Auto mode the first time it is active. Users who see the notice have no documentation explaining when it appears, why it appears only once, or how it relates to Auto mode availability.

Suggested Improvement

Update the VS Code settings table so allowDangerouslySkipPermissions only describes exposing Bypass permissions, not Auto mode.

Suggested replacement:

allowDangerouslySkipPermissions | false | Adds Bypass permissions to the mode selector. Use Bypass permissions only in sandboxes with no internet access. Auto mode appears independently when your account meets the Auto mode requirements.

Update the VS Code tab on the permission modes page to say Auto mode appears in the VS Code mode indicator when Auto mode is available for the account and environment, without requiring the bypass-permissions toggle.

Add a short note to the VS Code guide near the permission mode or new-session documentation:

The first time Auto mode is active for a new VS Code session, Claude Code shows a dismissable notice explaining what Auto mode does. Dismissing the notice does not disable Auto mode; use the mode selector to change modes.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

Total scope: 2 pages affected

Version context: v2.1.154 release entry: [VSCode] Auto mode no longer requires the bypass-permissions setting to appear in the mode picker, and a dismissable notice on the new-session screen explains auto mode the first time it's active.