[BUG] VSCode extension: 'Always allow' permission option truncates command text

Open 💬 2 comments Opened Jun 22, 2026 by tun0

What's Wrong?

When the Claude Code VS Code extension asks for permission to run a command, the second option ("Always allow") only shows the very beginning of the command — the rest is truncated and not readable. The first option (allow once) shows the full command, but the second option is cut off, making it impossible to verify what you are permanently allowing before clicking.

Note: #69552 covers a similar truncation issue in the TUI/terminal permission prompt. This is a separate occurrence specific to the VS Code extension UI.

What Should Happen?

The full command should be legible in the "Always allow" option — either by showing the complete text, wrapping it, or providing a hover/expand affordance — so users can make an informed decision before granting a permanent permission.

Steps to Reproduce

  1. Open a project in VS Code with the Claude Code extension active (native extension).
  2. Ask Claude to run a command with a moderately long invocation (e.g. kubectl get pods -n some-namespace --context some-context).
  3. Observe the permission prompt with the two options.
  4. Notice the "Always allow" option only shows the first few characters of the command; the rest is truncated.

Error Messages/Logs

No error — purely a UI legibility/truncation issue in the extension webview.

Claude Code Version

2.1.159 (Claude Code) — VS Code extension version: 2.1.181

Platform

Anthropic API

Operating System

Other Linux (Manjaro, kernel 6.12.91-1-MANJARO)

Terminal/Shell

VS Code native extension (not terminal)

Is this a regression?

I don't know.

Additional Information

The truncation is particularly problematic for the "Always allow" option since that action is permanent. Being unable to read the full command before granting a standing permission is both a UX and a security concern. A tooltip, text wrapping, or an expandable detail view would resolve this.

View original on GitHub ↗

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