Permissions issues on VS Code — page 2
Issues the maintainers labelled both platform:vscode and area:permissions.
176 issues · 33 open · 143 resolved (81%) · first seen Feb 23, 2026
Is this getting better or worse?
This class of problem is converging. 55 new reports in the last 90 days vs 111 in the 90 before — -50%. The open backlog peaked at 55 in 2026-03 and sits at 33 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
107 of these reports name the Claude Code build they were running, spanning 73 releases. Heaviest reporters:
- Claude Code v2.1.76
- Claude Code v2.1.233
- Claude Code v2.1.141
- Claude Code v2.1.119
- Claude Code v2.1.78
- Claude Code v2.1.63
- Claude Code v2.1.72
- Claude Code v2.1.241
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 33 days across 143 closures. Of the 143 closures with a recorded reason, 12% were closed as completed and 126 as not-planned or duplicate. The most recent completed fix landed in 2026-08.
Workarounds reported by the community
38 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 - [Feature Request] Add setting to skip protected directory prompts when bypassPermissions is enabled
- …ns involve many edits to , , , and occasionally . Attempted Workarounds (all failed) 1. patterns (e.g. ) — do not override the protected directory prompt 2. hook returning — does not fire in VS Code extension (see 13203,…
Found in the description of #35942 · 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 101–176
Ranked by community engagement (reactions weighted over comments).
- VS Code extension still prompts for file writes despite allowDangerouslySkipPermissions
- [BUG] Permission mode resets to different mode when switching editor tabs via Ctrl+Tab / Ctrl+Shift+Tab
- VSCode extension ignores bypassPermissions defaultMode setting
- VS Code extension: "Trust mode" or equivalent of --dangerously-skip-permissions
- [FEATURE] VSCode extension: actionable permission prompts directly in notifications (no tab switch required)
- [Bug] additionalDirectories from settings.local.json not loaded in permissions
- [BUG] "Allow for all projects" permission not applied to pending MCP requests in same session
- [BUG] Bash permissions are ignored
- Bash permission `allow` rules (wildcard and exact-match) never suppress prompts on WSL project opened via `\\wsl$` UNC path (VSCode WSL Remote)
- [BUG] Claude Code VS Code Extension ignoring settings.json permissions
- [Bug] Agent deletes empty directories in plan mode without confirmation
- [VSCode extension] Allow configuring permission mode after plan approval
- Project-scope permission grant strips unknown top-level keys from .claude/settings.json
- [BUG] Auto-mode permission levels don't compact context.
- [DOCS] VS Code auto mode docs still tie mode-picker visibility to bypass-permissions setting
- Auto-mode classifier blocks explicit user imperative: 'push to main'
- [MODEL] Prevent Claude code from scanning the repo automatically before being asked!
- Feature request: allow disabling bypass permission mode entirely
- [BUG] CRITICAL: Bash permission gate bypassed for compound `rm -rf … && … | … ; echo …` commands in default mode (no allow-list match, no prompt shown, reproduced on 2.1.139)
- Plan mode does not restrict tool access when controlling a desktop session via remote control from mobile
- VS Code: "Yes, allow … for all projects" never suppresses prompt for files outside workspace folder
- [BUG] Bash permission picker truncates focused option's typed text in VSCode integrated terminal
- [FEATURE] expose setPermissionMode as a public VS Code command
- [Bug] Auto-run migrations without user confirmation
- [Bug] File deletion confirmation still blocks after explicit approval
- [BUG] Claude Code violated .gitignore/.claudeignore policy by reading .env file using Bash cat command in auto-approve mode
- VS Code extension: orange UI chrome desaturates to gray after "Yes, don't ask again for session" permission choice
- [VS Code] initialPermissionMode: "bypassPermissions" is ignored on new conversations
- Approved permission prompts not surfaced to Claude in conversation
- [BUG]
- [BUG] Claude Code edits my files without asking, despite "Ask Before Edits" being on
- [FEATURE] Allow vscode extension to save runtime grants in local settings / project settings
- [BUG] WebFetch permission denied in "Ask before edits" mode (VSCode extension)
- getInitialPermissionMode() inspect() ignores Machine-level settings from devcontainer.json
- [BUG] Claude Code for VSCode memory regression in 2.1.78
- Missing trust/permission prompt in VSCode/Positron extension vs CLI
- [MODEL]
- [BUG] managed-setting.json is bypassed when using Claude in VSCode combined with remote-ssh
- [BUG] autoAllowBashIfSandboxed regression in v2.1.70+ VSCode extension — write commands prompt despite sandbox
- VS Code: deny in settings should prevent MCP tools from loading into context, not just block execution
- permissions: Bash(rm -r:*) does not match rm -rf
- Permission deny rules can be bypassed via Bash recursive grep and Glob filename listing
- [BUG] "Don't ask again for similar commands" saves verbatim command strings, so near-identical commands re-prompt every time
- [BUG] While in Plan mode, it writes files
- [BUG] Tool approval settings ignored causing excessive approval prompting
- PreToolUse hook's empty stdout forces an interactive prompt, ignoring an existing allow rule (VS Code extension)
- [BUG] Claude performed actions that were not approved
- [BUG] permission dialog text truncated
- [Bug] Model fabricates user approval and executes destructive operations in plan mode
- Permission prompt dialogs not localized (always shown in English) despite VS Code locale set to Japanese
- [Bug] Guard prevents code execution and causes loss of work/commits
- [BUG] confirmation prompts preempt enter key for sending additional text
- [BUG] Permission request dialog hides chat
- AskUserQuestion intermittently shows a permission prompt despite bypassPermissions + allow rule (VS Code extension)
- [BUG] Claude autonomously ran background scripts calling a paid external API, causing ~$29 unintended charge
- [Bug] VSCode: exiting plan mode ignores permissions.defaultMode: "auto" and silently lands in acceptEdits (no choice offered)
- [FEATURE] Use a unique color code for the 'Auto Mode' feature
- VS Code: moving chat from side panel to main window breaks modals and resets permissions
- `acceptEdits` mode does not extend to `additionalDirectories` (Edit/Write still prompt per-file)
- defaultMode: acceptEdits silently overrides per-path permissions.ask rules for Write/Edit
- [FEATURE] Manual confirmation new option
- [BUG] VS Code extension drops Auto from the mode picker when user-settings model is an alias absent from the models list (e.g. "opus") — availability stuck at "unknown"
- [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
- [BUG] Tool permission stream closes intermittently in VS Code extension (still occurring on 2.1.241) — related to #44157
- [MODEL] CRITICAL PERMISSION BYPASS: Claude manufactures its own execution authority from a document it wrote, overrides an explicit in-context user prohibition, and runs unapproved privileged commands
- VS Code extension: AskUserQuestion picker steals keyboard focus on mount even when its chat tab is hidden (mount-focus lacks the document.hasFocus gate the 500ms step has)
- [BUG] Auto mode missing from permission mode picker on Fable 5 (VS Code extension, Windows)
- VS Code extension: PreToolUse 'ask' permission tier (static rules + hooks) silently resolves to allow, no prompt shown
- [BUG] Agent unilaterally created/rotated a production API credential without asking
- [BUG] Edit permission prompt still fires despite bare Edit/Edit(**) allow rules and global bypassPermissions mode
- Auto-generated permission entries in `.claude/settings.local.json` contain malformed globs (dead entries)
- [Bug] Auto-generated permission rules override explicit user-requested constraints
- [BUG] VSCode extension for Claude: mode selection has no effect on current session
- [BUG] Edit Automatically mode not working correctly.