VS Code Extension Ignores Global dangerously-skip-permissions Setting

Open 💬 25 comments Opened Jul 3, 2025 by fwends

Bug Description
Subject: VS Code extension ignores dangerously-skip-permissions global setting

Description:
The Claude Code VS Code extension does not respect the dangerously-skip-permissions setting from the global configuration file, causing constant permission prompts that disrupt workflow.

Environment:

  • Claude Code CLI version: 1.0.40
  • VS Code extension version: 1.0.41 (also tested with 1.0.40)
  • macOS Version: 15.5.0 (Build 24F74)
  • VS Code version: 1.101.2

Configuration:
Global settings file at ~/.claude/settings.json:
{
"model": "sonnet",
"dangerously-skip-permissions": true,
"permissions": {
"allow": ["*"],
"deny": [...]
}
}

Project-specific settings also tested at /path/to/project/.claude/settings.local.json with same configuration.

Expected Behavior:
With dangerously-skip-permissions: true, commands should execute immediately without permission prompts in both CLI and VS Code extension.

Actual Behavior:

  • CLI version: Works correctly, executes commands without prompts
  • VS Code extension: Ignores the setting, shows permission dialog for every command

Steps to Reproduce:

  1. Set "dangerously-skip-permissions": true in global settings
  2. Start Claude Code CLI - commands execute without prompts ✓
  3. Use Claude Code in VS Code - still shows permission dialogs ✗

Impact:
This makes the VS Code extension unusable for productive development as every command requires manual approval, defeating the purpose of the dangerous permissions flag.

Additional Notes:
The extension appears to use its own permission handling system that doesn't read or respect the global configuration file settings.

Environment Info

  • Platform: darwin
  • Terminal: iTerm.app
  • Version: 1.0.40
  • Feedback ID: 0c15f7c0-52c9-4928-ab7b-f6c6908ea500

Errors

[{"error":"Error: Command failed: security find-generic-password -a $USER -w -s \"Claude Code\"\nsecurity: SecKeychainSearchCopyNext: The specified item could not be found in the keychain.\n\n    at genericNodeError (node:internal/errors:983:15)\n    at wrappedFn (node:internal/errors:537:14)\n    at checkExecSyncError (node:child_process:892:11)\n    at execSync (node:child_process:964:15)\n    at FI (file:///Users/greg/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:702:3921)\n    at file:///Users/greg/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:623:9038\n    at Q (file:///Users/greg/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:526:13327)\n    at _X (file:///Users/greg/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:623:8184)\n    at H_ (file:///Users/greg/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:623:7265)\n    at U9 (file:///Users/greg/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:623:11432)","timestamp":"2025-07-02T04:37:23.360Z"},{"error":"Error: Command failed: security delete-generic-password -a $USER -s \"Claude Code\"\nsecurity: SecKeychainSearchCopyNext: The specified item could not be found in the keychain.\n\n    at genericNodeError (node:internal/errors:983:15)\n    at wrappedFn (node:internal/errors:537:14)\n    at checkExecSyncError (node:child_process:892:11)\n    at execSync (node:child_process:964:15)\n    at FI (file:///Users/greg/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:702:3921)\n    at mpA (file:///Users/greg/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:623:10150)\n    at hpA (file:///Users/greg/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:623:10024)\n    at p9A (file:///Users/greg/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:2158:2567)\n    at l9A.startOAuthFlow (file:///Users/greg/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:2158:3689)\n    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)","timestamp":"2025-07-02T04:37:37.268Z"},{"error":"Error: Command failed: security find-generic-password -a $USER -w -s \"Claude Code\"\nsecurity: SecKeychainSearchCopyNext: The specified item could not be found in the keychain.\n\n    at genericNodeError (node:internal/errors:983:15)\n    at wrappedFn (node:internal/errors:537:14)\n    at checkExecSyncError (node:child_process:892:11)\n    at execSync (node:child_process:964:15)\n    at FI (file:///Users/greg/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:702:3921)\n    at file:///Users/greg/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:623:9038\n    at Q (file:///Users/greg/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:526:13327)\n    at _X (file:///Users/greg/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:623:8184)\n    at H_ (file:///Users/greg/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:623:7265)\n    at U9 (file:///Users/greg/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:623:11432)","timestamp

Note: Error logs were truncated.

View original on GitHub ↗

25 Comments

nimbah · 12 months ago

Open the claude code extension & hit Command+C and run claude --dangerously-skip-permissions

easier tbh

fwends · 12 months ago
Open the claude code extension & hit Command+C and run claude --dangerously-skip-permissions easier tbh

I have that set up as an alias and type ccc to run it in the terminal that's not what the report here is about.

deromka · 9 months ago

Increase priority for this ticket, since with the newly updated Claude Code VSCode extension, the workaround with Ctrl+C and running 'claude --dangerously-skip-permissions' it does not work anymore. I've tried setting an alias in zshrc, but it does not work since extensions are not loading up the shell, I've tried adding this flag to ~/.claude/settings.json, it did not work.

silver-epsilo · 9 months ago

+1 -- Claude Code VSCode extension no way to workaround

fwends · 9 months ago

Absolutely crap this vscode extension update it's made it not even usable now. Typical of anthropic just gimmicks all the time. Locking up the extension like this so we can even exit it. This is very very bad design

deromka · 9 months ago
Absolutely crap this vscode extension update it's made it not even usable now. Typical of anthropic just gimmicks all the time. Locking up the extension like this so we can even exit it. This is very very bad design

I assume its really a VS Code extension, rather than just running a shell inside the extension as was in a first version

FredLackeyOfficial · 9 months ago

+1 ... horrible update

silver-epsilo · 9 months ago

Have to reverse to 1.0.127 since 2.0.1 have no workaround for dangerously-skip-permissions

fwends · 9 months ago
Have to reverse to 1.0.127 since 2.0.1 have no workaround for dangerously-skip-permissions

Agreed, i did the same and then turned off updates

lightme16 · 9 months ago

+1 that's hugely impacted my productivity with CC. Please I provide a work around for adding dangerously-skip-permissions for allowlisted sessions.

jimmy927 · 9 months ago

This was seriously slowing me down so much i build a patcher to fix the issue.

Find it here:

https://github.com/jimmy927/claude-code-extension-patcher

PS C:\Users\jimmy\src\claude-code-extension-patchger> .\ultra-yolo-patcher.ps1  -yes
Claude Code YOLO Patcher - Dual Mode (Windows + WSL)

[1/2] Windows...
[FOUND] C:\Users\jimmy\.cursor\extensions\anthropic.claude-code-2.0.10-universal (3 files)
[FOUND] C:\Users\jimmy\.vscode\extensions\anthropic.claude-code-1.0.109 (1 files)
Patched 4/4 files
RESTART Cursor/VSCode!
Logs: C:\Users\jimmy\AppData\Local\Temp\claude-code-yolo.log

[2/2] WSL...
[FOUND] /home/jimmy/.cursor-server/extensions/anthropic.claude-code-2.0.10-universal (3 files)
[FOUND] /home/jimmy/.cursor-server/extensions/anthropic.claude-code-2.0.14-universal (3 files)
Patched 6/6 files
RESTART Cursor/VSCode!
Logs: /tmp/claude-code-yolo.log
PS C:\Users\jimmy\src\claude-code-extension-patchger>
kdoran · 9 months ago

I'm on mac and same thing, the latest vs code claude code extension update seems to ignore any flavor of https://docs.claude.com/en/docs/claude-code/settings

If I so much as open a new chat window, it's back to "Make this edit to [file]?"

shanegriffiths · 9 months ago

👍🏼 Please get this resolved.

fwends · 9 months ago

Get Claude to edit the extension so that it just uses the terminal with bypass mode. So now when I press Claude icon in vscode it opens the terminal up in the same window of what Claude code would be embedded in vscode and runs it. Much better than their horrible gui extension. Gives you back the cli properly

thalesfsp · 8 months ago

When this will be fixed?

jimmy927 · 8 months ago

Solved in 2.0.35

<img width="1274" height="827" alt="Image" src="https://github.com/user-attachments/assets/3fd06915-09a8-4d9c-9bcf-dca714ba3b6f" />

pzgz · 7 months ago

Sadly, the issue is still there time to time, 2.0.50 now. Still asking for permissions time 2 time. Even you select don't ask again in this session, it's still asking

Solved in 2.0.35 <img alt="Image" width="1274" height="827" src="https://private-user-images.githubusercontent.com/3243901/511687043-3fd06915-09a8-4d9c-9bcf-dca714ba3b6f.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjM4NzQ4NzIsIm5iZiI6MTc2Mzg3NDU3MiwicGF0aCI6Ii8zMjQzOTAxLzUxMTY4NzA0My0zZmQwNjkxNS0wOWE4LTRkOWMtOWJjZi1kY2E3MTRiYTNiNmYucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MTEyMyUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTExMjNUMDUwOTMyWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZDM0ZmVlMjJiYjlhYzY0MTZkYTI5ODU1YTFlYWY2NDgzZjFlMjRjZGI2OTcyMGI3NmVhMGRjNWU4NWY3ZTY0NyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.2HMCsJn__SJEHO6BqCrTtAbM9P-3aP4wlwz3R7cd43M">
github-actions[bot] · 6 months ago

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

moritzWa · 5 months ago

Still not working on v2.1.19 (Cursor). Tried everything:

  • ~/.claude/settings.json with "permissions": { "defaultMode": "bypassPermissions" }
  • Cursor/VS Code settings: claudeCode.allowDangerouslySkipPermissions: true + claudeCode.initialPermissionMode: "bypassPermissions"
  • Enabled both via Settings GUI
  • Restarted editor, started new conversations

Still prompts for web search and other non-edit actions. Only file edits can be auto-accepted via the inline "Edit automatically" option.

Uriel1339 · 4 months ago

Mine still reverses from time to time back from BypassPermissions to asking for permission...

cidoliveira · 4 months ago

any update? it's really annoying to use GSD and having to click to accept every single prompt

chasel5050 · 4 months ago

I'm still experiencing this error with VS Code. All bypass permissions are selected and the mode property changed, but still getting prompted for approvals. Any work around without switching to a different terminal or software?

AAChartModel · 1 month ago

Any solution here? 👀

cidoliveira · 1 month ago

@AAChartModel VSCode extension now has auto mode and bypass permissions. Bypass permissions is the same as terminal --dangerously-skip-permissions.

<img width="308" height="341" alt="Image" src="https://github.com/user-attachments/assets/19868221-1d07-4e15-90ce-9acb31435858" />

AAChartModel · 1 month ago

@cidoliveira Thanks, it works for me now!