[FEATURE] Yes, and bypass permissions

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Problem Statement
When using Plan Mode in the VSCode extension with allowDangerouslySkipPermissions enabled, the plan acceptance prompt only offers two execution options:

Yes, and auto-accept
Yes, and manually approve edits

<img width="873" height="316" alt="Image" src="https://github.com/user-attachments/assets/fdb7fe57-d426-4105-8094-d268d10556e7" />

To execute the plan with bypass permissions, I have to accept using one of the existing options and then manually switch to "Bypass permissions" mode via the prompt dropdown menu:

<img width="945" height="408" alt="Image" src="https://github.com/user-attachments/assets/69e9f3d6-b0b7-494e-b5ef-fb4990aa9287" />

Forgetting to change this setting after accepting the plan is probably the most common reason that claude gets stuck in my workflow.

The cli does offer "Yes, and bypass permissions" as one of the plan acceptance prompt options when started with --allow-dangerously-skip-permissions:

<img width="1027" height="876" alt="Image" src="https://github.com/user-attachments/assets/9860b3d6-55fe-4ed5-b03c-8db5ed0e829b" />

Proposed Solution

When allowDangerouslySkipPermissions is enabled, add a third Accept option to the plan acceptance prompt in vscode which matches the "Yes, and bypass permissions" option available in the CLI.

Alternative Solutions

Align to the CLI behavior by replacing the "Yes, and auto-accept" option with a "Yes, and bypass permissions" option when allowDangerouslySkipPermissions is enabled

Priority

Low - Nice to have

Feature Category

Other

Use Case Example

I almost always run Claude code in VS Code inside a devcontainer, with a repo I fully control. I've never intentionally rejected a command. I typically use plan mode to iterate on a plan until I'm satisfied and then turn Claude code loose to implement it, and come back later. When it's done I review the local commits and iterate interactively.

Moderately often, I come back to find claude stuck waiting for me to approve an innocuous command rather than with a complete commit ready for my review. I'd like to remove that opportunity for human error from my workflow.

Additional Context

Related Issues:

#5466 is about changes to behavior in plan mode with bypass permissions enabled, rather than the transition between plan and bypass permissions modes.

#29565 is about bypass permissions working at all from mobile. This is purely about the desktop VSCode interface

#19426 is about documentation for the CLIs additional context clearing options. This is purely about selecting which mode to enter when leaving plan mode, not about context.