### Preflight Checklist - [x] I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) and this hasn't been reported yet - [x] This is a single bug report (please file separate reports for different bugs) - [x] I am using the latest version of Claude Code ### What's Wrong? When Claude Code requests permissions in the VSCode extension, the permission dialog shows three options: 1. Yes 2. Yes, allow for for session (something

[BUG] VSCode Extension Permission Dialog Text Ellipsized

Status Closed — not planned

Reported on v2.1.20

Maintainer reply None cached

Activity 6 comments · opened Jan 27, 2026 · closed Mar 7, 2026

Preflight Checklist

[x] I have searched existing issues and this hasn't been reported yet
[x] This is a single bug report (please file separate reports for different bugs)
[x] I am using the latest version of Claude Code

What's Wrong?

When Claude Code requests permissions in the VSCode extension, the permission dialog shows three options:

Yes
Yes, allow for for session (something like "Allow [action] on [path] for this session")
No

The problem: The text for the middle option ("Allow for session") is always ellipsized (truncated with "..."), even when there is plenty of horizontal space available in the dialog to display the full text (see screenshot):

What Should Happen?

It should use the full width of the button to actually display the full path and command.
Also, if there's not enough space it should be possible to show the full thing in a button overlay.

Error Messages/Logs

Steps to Reproduce

Open VSCode with the Claude Code extension installed
Start a Claude Code session
Ask Claude to perform an action that requires permission (e.g., read a file, run a bash command)
When the permission dialog appears, observe the three options
Note that the middle option text is ellipsized even though the dialog has sufficient width to display the full text

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.20 (of the VSCode plugin)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗

6 Comments

IshayF · 8 months ago

MrVPlusOne · 8 months ago

Can confirm this is a real usability (and arguably security) issue. I hit this daily with bash command permissions — the option shows something like:

Yes, allow //Users/username/... for this session

With the rule truncated, I have no idea whether I'm granting Bash(/Users/username/Code/my-project:*) or Bash(/Users/username:*) — those are very different permission scopes. I end up falling back to option 1 ("Yes") every time because I can't trust what option 2 is actually enabling, which defeats the purpose of session-level permissions entirely.

The terminal/CLI does not have this problem — the full rule is always visible there.

Suggested fix: VS Code's QuickPickItem API supports a detail property that renders a second line below the label. This could be used to display the full permission rule without being constrained by the single-line label width:

{
  label: "Yes, allow for this session",
  detail: "Bash(/Users/username/Code/my-project:*)"
}

This would be a minimal change that fully solves the problem.

github-actions[bot] · 7 months ago

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

IshayF · 7 months ago

Was a new issue opened for this?

yannbolliger · 7 months ago

Yes, this is still a problem

github-actions[bot] · 6 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.