[BUG] VSCode extension: PowerShell permission prompt only shows Yes/No — missing "allow for session/project/always" options

Description

When Claude Code in the VSCode extension prompts for permission to run a PowerShell
command, the prompt only offers two options: Yes and No. The broader approval
options available in the CLI terminal — such as "Allow for this session",
"Allow for this project", or "Always allow" — are completely absent.

This makes it impossible to approve a class of PowerShell commands persistently
without manually editing settings files.

Steps to Reproduce

1. Open a project in VSCode with the Claude Code extension installed
2. Ask Claude to run any PowerShell command
3. Observe the permission prompt

Expected Behavior

The permission prompt should offer the same options as the CLI terminal:

• Yes (once)
• Yes, allow for this session
• Yes, allow for this project
• Yes, always allow
• No

Actual Behavior

The permission prompt only shows:

• Yes
• No

There is no way to approve a command more broadly than once from within the prompt itself.

Environment

• OS: Microsoft Windows 11 Enterprise 10.0.26200 Build 26200
• Claude Code VSCode extension version: 2.1.160
• VSCode version: 1.122.1 (x64)
• Shell: PowerShell 7.6.2 (pwsh)
• Claude Code CLI version: 2.1.158 (may not be used by the extension)

Impact

Every PowerShell command requires manual approval one by one. The only workaround
is to manually edit .claude/settings.local.json or ~/.claude/settings.json
with the appropriate allow rules — which is undiscoverable and error-prone.

Related Issues

• #32973 — Feature request for persistent "Always allow" from the prompt (CLI)
• #33047 — VSCode extension ignores "Allow for this session" (but at least shows

the option)