Permissions issues on VS Code — page 3
Issues the maintainers labelled both platform:vscode and area:permissions.
227 issues · 61 open · 166 resolved (73%) · first seen Feb 23, 2026
Is this getting better or worse?
This class of problem is holding steady. 70 new reports in the last 90 days vs 77 in the 90 before — -9%. The open backlog peaked at 61 in 2026-10 and sits at 61 today.
Derived by counting each matching issue from its creation date until it closed. First-party
computation over the anthropics/claude-code tracker — the trend is not published
anywhere upstream.
Which builds report this
148 of these reports name the Claude Code build they were running, spanning 98 releases. Heaviest reporters:
- Claude Code v2.1.76
- Claude Code v2.1.289
- Claude Code v2.1.296
- Claude Code v2.1.282
- Claude Code v2.1.270
- Claude Code v2.1.263
- Claude Code v2.1.233
- Claude Code v2.1.141
Report volume, not a defect count: an issue can mention a build without that build having caused the failure. Versions come from the version string in the bug-report template, matched against real published tags.
Do these get fixed?
Median time to close is 34 days across 166 closures. Of the 166 closures with a recorded reason, 10% were closed as completed and 149 as not-planned or duplicate. The most recent completed fix landed in 2026-08.
Workarounds reported by the community
54 of these issues post a workaround someone says worked. The highest-engagement ones:
- [BUG] Bypass/dangerously skip permissions now broken in all Claude Code versions newer than v2.1.77
- Update: The PreToolUse hook workaround (returning for protected directories) does NOT work on v2.1.81 / Windows 11. The hook fires and logs the auto-approve (confirmed via audit log), but the binary-level protected-direc…
Found in the thread of #36168 · still open - [BUG] Bash comments break permissions
- Workaround: a PreToolUse hook can strip the comment lines before permission matching sees them. The hook reads the command, removes leading lines, and returns the clean command via . Your allowlist then matches correctly…
Found in the thread of #29582 · resolved - bypassPermissions mode still prompts for edits to ~/.claude/ files
- …e could modify these, it could escalate its own permissions Workaround: Use a PreToolUse hook that auto-approves edits to specific \ subdirectories you trust: \ \ \ This selectively allows edits to \ and \ while keeping…
Found in the thread of #37253 · resolved - [BUG] UNC paths in working directories cause settings.json permissions to be ignored
- …ed paths in settings causes all permission lookups to fail. Workaround: Ensure all configured working directories resolve to mapped drive letters rather than UNC paths, or avoid adding UNC paths to the additionalWorkingD…
Found in the description of #29935 · resolved - Permission mode resets from 'Bypass permissions' to 'Edit automatically' mid-session
- …(slash commands / skills that expect unattended operation) Workaround Setting in under the key causes the mode to reset to Bypass instead of Edit Automatically. This mitigates but doesn't prevent the reset. Environment…
Found in the description of #39057 · resolved
Excerpts are quoted from the linked issue so you can judge relevance before opening it. Threads that only ask for a workaround, or report that there is none, are excluded. These are community suggestions, not official guidance from Anthropic — read the full thread before applying one.
Matching issues 201–227
Ranked by community engagement (reactions weighted over comments).
- [Bug] Auto mode safety check blocks writing skill files
- [Bug] Auto mode blocks harmless actions like reading project context files
- [Bug] Claude Code Refuses SSH Connection to User's Own Linux Device
- Claude Code keeps prompting for approval (found workaround) on git fetch/pull/remote/reflog/ls-files despite matching Bash allow-list wildcard entries.
- [Bug] Claude Code executed privileged command without explicit user consent, rotating API credentials
- [FEATURE] Allow trusting specific UNC network shares
- [Feature Request] Restore full UI testing capabilities with expanded tool permissions
- [BUG] Windows: VS Code extension ignores project permissions.allow because workspace trust is keyed by drive-letter case (c: vs C:)
- [Bug] Safety check blocks all SSH commands after credential materialization denial, no way to clear it
- [BUG] VSCode extension ignores ~/.claude/settings.json permissions.allow rules and prompts for permissions on all Bash commands despite correct Bash(cmd:*) syntax
- I don't have enough context to generate an appropriate GitHub issue title. Could you please provide: 1. **The specific problem or bug** you encountered 2. **Error messages** (if any) 3. **What you were trying to do** when the issue occurred 4. **Expected
- [Bug] Claude Code posted false bug report to public repository without user consent
- VSCode extension: no hook fires when user rejects a tool permission prompt
- VS Code panel hardcodes the plan-approval buttons to acceptEdits/default, so the CLI's "Yes, and use auto mode" row never appears
- VS Code panel silently drops Auto from the permission-mode picker while the extension host reports canEnterAuto=true
- [Bug] Manual approval of blocked action not persisting; [Credential Exploration] denial recurring on retry
- Text typed in the permission-deny dialog is lost when denying one of several parallel Agent tool calls (VS Code extension, 2.1.263)
- Resumed sessions silently lose capabilities after upgrades (e.g. Auto permission mode missing from picker while its classifier is active)
- [BUG] git diff --unified=0 / -U0 triggers a permission prompt despite being read-only
- Permission dialog presents machine-composed commands as unreadable monochrome text
- [Feature Request] Reduce excessive user prompts in auto mode
- Bash allow rules written project-relative do not match the same script invoked by its absolute path under the project directory
- VSCode extension: 'always allow' permission grants written to tracked .claude/settings.json instead of gitignored settings.local.json
- [FEATURE] Manual confirmation new option
- [BUG] VS Code extension: rejecting a queued edit with a reason still forces review of all remaining queued edits before control returns to the model
- [BUG] VS Code extension: after approving one of several queued edit approvals, chat scrolls to bottom instead of the next pending edit
- [BUG] Instalation without permission