Permissions issues on VS Code
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 112 in the 90 before — -51%. 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 1–100
Ranked by community engagement (reactions weighted over comments).
- [BUG] Bypass/dangerously skip permissions now broken in all Claude Code versions newer than v2.1.77
- [BUG] Bash comments break permissions
- bypassPermissions mode still prompts for edits to ~/.claude/ files
- [BUG] VSCode extension repeatedly asks for permission to edit the same file, even if Allow for this session is selected.
- VS Code: Edit tool prompts for permission despite bypassPermissions mode
- [BUG] UNC paths in working directories cause settings.json permissions to be ignored
- [Bug] Plan mode incorrectly requests permissions for non-destructive operations like explore and Bash commands
- [Feature Request] Add setting to skip protected directory prompts when bypassPermissions is enabled
- Permission mode resets from 'Bypass permissions' to 'Edit automatically' mid-session
- [Bug] Plugin skills prompted for Read permission on their own plugin directory files
- [BUG] 2.1.114 regression: background subagents cannot write to paths listed in permissions.allow — works in 2.1.112
- [BUG] Bypass Permissions Mode will still require permissions for memory & skill edits
- VS Code extension ignores Bash permission allow rules from settings.json
- VS Code extension ignores Edit/Write permission rules in settings files
- Claude runs explicitly forbidden destructive git commands, ignores own memory rules, destroys user work twice in same session
- [BUG] PermissionDecision in PreToolUse is ignored in latest VS Code Extension
- [BUG] Bypass permissions not working in Antigravity/VS Code Remote SSH despite all configurations (v2.1.73)
- [BUG] In "Ask before edit" permission mode, Claude Code executes Edit/Write tool calls without displaying a confirmation prompt to the user. Multiple files were modified across several tool calls with no opportunity to approve or deny.
- PreToolUse(Bash) hook returning permissionDecision: "defer" causes "[Tool result missing due to internal error]"
- Feature request: Sound notification for permission prompts in VSCode panel
- VS Code: initialPermissionMode setting not respected — always defaults to 'Edit automatically'
- [BUG] settings.json or settings.local.json do NOT suppress permission prompts
- VSCode extension: repeatedly asks permission for already-allowed git commands (Opus 4.6)
- [BUG] VSCode extension does not enforce permissions from ~/.claude/settings.json -
- Side-effecting actions (gh PR replies, git push) run without announcement or confirmation
- [BUG] Extension crashes (exit code 1) when allowDangerouslySkipPermissions is set and running as root
- [BUG] VSCode extension: plan approval with "Yes, and auto-accept edits" enters acceptEdits instead of Auto mode (terminal enters Auto mode)
- Model re-attempts denied tool call after user explicitly says 'no'
- Opus 4.7: Excessive confirmation friction blocks autonomous workflows — regression vs Sonnet 4.6
- MCP destructive tools silently denied without prompt in acceptEdits mode — misleading error message
- [DOCS] VS Code docs missing guidance for settings.json parse failures disabling permission rules
- [BUG] Bash tool bypasses settings.json path deny rules — shell commands not subject to file tool access controls
- VSCode extension: permission mode resets from bypassPermissions to auto/acceptEdits mid-conversation
- VS Code: Tool approval popup should not steal focus from active text input
- VS Code extension 2.1.131 silently ignores `claudeCode.initialPermissionMode` and `claudeCode.claudeProcessWrapper` (regression vs 2.1.128)
- bypassPermissions mode not persisted — resets mid-session and prompts for file edits
- [FEATURE] [VS CODE EXT] Add back the option to set to Bypass Permissions automatically after accepting plan
- [BUG] Title: CLAUDE.md project rules overridden by MCP server instructions — runaway token consumption
- [BUG] Tool restrictions from claude.ai are ignored by the CLI / VS Code extension
- [BUG] Auto mode missing from VS Code extension picker on Linux despite canEnterAuto=true (works in terminal CLI and Windows extension)
- [BUG] Claude Code — Per-Agent Permission Control Gap
- [FEATURE] Allow collapsing the code preview in permission prompts (VS Code extension)
- permissions.allow in project .claude/settings.json is ignored by VS Code extension
- Claude Code performs destructive actions beyond the scope requested by the user
- [BUG] VSCode extension ignores all managed settings (managed-settings.json, MDM profile, user settings.json) on macOS
- [BUG] Permission parser treats # in multi-line quoted strings as shell comments
- [BUG] Sub-agent permission mode inheritance broken — permissionMode frontmatter and parent acceptEdits both ineffective for Edit tool calls
- [BUG] VSCode 2.1.139: acceptEdits / Edit automatically mode still prompts for Edit tool approval (regression persists since v2.1.79)
- Bash tool executed `brew install` without prompting user for approval
- [BUG] Claude Code Caused Production Server Outage and Data Loss
- [Bug] Temporary directory access permissions not enforced
- [Bug] Bypass permission mode still prompts for permissions
- Read tool bypasses PreToolUse hooks and permissions.deny rules in VSCode extension
- acceptEdits mode still prompts for files in .claude/ directory (workspace root)
- Permissions bypassed and not persisted in VS Code/Cursor extension
- [DOCS] VS Code docs missing permission-picker behavior when `disableBypassPermissionsMode` is set
- [BUG] VSCode extension: PowerShell permission prompt only shows Yes/No — missing "allow for session/project/always" options
- [BUG] VSCode extension requests permissions for commands already approved
- [BUG] Permission-suggestion UI generates malformed rule (unclosed quote) for git commit heredoc patterns; sometimes crashes the dialog
- VSCode/Cursor extension: permission-IPC race kills sessions, error rendered as "[object Object]"
- [Bug] Agent self-approves and executes write operations without awaiting user confirmation
- [BUG] When Bash(mkdir:*) is listed in allowed-tools, Claude still prompts for permission
- "[BUG] initialPermissionMode: acceptEdits" and "Allow for this session" not persisting in VSCode extension
- Bash tool prompts for approval despite matching allow-list rule + defaultMode: bypassPermissions
- Transport loss writes a fabricated user denial into the session transcript
- [FEATURE] Expose bypass permissions in the VS Code extension via a per-session, type-to-confirm gate
- [BUG] Subprocess 60000ms timeout on startup when permission allow rules reference temporarily unmounted drives (Windows)
- [Windows] Buffered keypress auto-approves plan/permission prompts after window switch or login
- [BUG]
- Edit tool bypassed 'ask before edit' permission mode
- [Bug] Claude Code commits and pushes changes without explicit user approval
- Granting a permission from the VS Code extension requires hand-editing JSON
- [BUG] Deny List not Honored for Edit/Write
- v2.1.121 VSCode native extension: permissions.deny rules not enforced
- [Bug] File operations execute with Accept Edits disabled
- Claude collapsed a staged-rollout approval into a batch execution, bypassing the verification gate the user explicitly asked for
- [BUG] Edit permission in settings.local.json not respected - confirmation dialog still appears
- [BUG] Plan mode prompts for permission on already-allowed read-only Bash commands
- [BUG] allowedTools restrictions not enforced — Claude reads files without approval prompt
- [BUG] VSCode Extension: Bash commands execute without permission prompt despite 'default' Initial Permission Mode on macOS
- [BUG] Security violation by design - leaking project details, memory on global scale
- [MODEL] Sonnet 4.5 Generates bash non Claude format wildcard glob patterns into settings.json
- [BUG] Claude Code ignoring auto accept edits mode
- VSCode Extension: Restored chat sessions ignore defaultMode on workspace reload
- [BUG] VSCode extension repeatedly asks for permission to edit files, even if Auto is selected
- [BUG] "Don't ask again" approvals write to project-shared .claude/settings.json instead of .claude/settings.local.json
- [BUG] VSCode extension: 'Always allow' permission option truncates command text
- [Bug] Unauthorized autonomous merge with admin override bypassed branch protection
- Write tool fails immediately in local VS Code despite Write(**) in permissions.allow — Edit works fine
- VS Code extension ignores settings.json allow list and bypassPermissions for UNC network path file edits
- [BUG] Unauthorized git push to production
- [BUG] "Allow Dangerously Skip Permissions" overrides plan mode in VS Code extension
- [BUG] AskUserQuestion permission stream closes before response - "Unhandled case: [object Object]" in VS Code extension
- [BUG] "Edit/Write permission prompts in VS Code extension missing 'Always allow' option"
- Opus 4.6 Self-report: I ignored user's permission prompt comments twice and continued with flawed approach — comment box feedback not reliably processed
- Agent Teams: Permission requests should show as native UI popups in VS Code extension, not as chat messages
- [Bug] Claude Code deleted Looker dashboards without confirmation or safety check
- Bash permission gate fires inconsistently in VS Code Claude extension — fails open on some commands not in allow list, fails closed on some commands that ARE in allow list
- [BUG] additionalDirectories approved in one project leak into all projects via global settings (project contamination)
- [BUG] Background subagent tool calls silently denied — permission dialog never surfaced