Skip to content

VS Code Extension Ignores Global dangerously-skip-permissions Setting #2933

Description

@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.

Activity

  1. nimbah commented on Jul 18, 2025

    @nimbah

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

    easier tbh

  2. fwends commented on Jul 18, 2025

    @fwends
    Author

    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.

  3. deromka commented on Sep 30, 2025

    @deromka

    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.

  4. silver-epsilo commented on Oct 1, 2025

    @silver-epsilo

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

  5. fwends commented on Oct 1, 2025

    @fwends
    Author

    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

  6. deromka commented on Oct 1, 2025

    @deromka

    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

  7. FredLackeyOfficial commented on Oct 2, 2025

    @FredLackeyOfficial

    +1 ... horrible update

  8. silver-epsilo commented on Oct 2, 2025

    @silver-epsilo

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

  9. fwends commented on Oct 2, 2025

    @fwends
    Author

    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

  10. lightme16 commented on Oct 2, 2025

    @lightme16

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

  11. 4 remaining items

  12. thalesfsp commented on Oct 22, 2025

    @thalesfsp

    When this will be fixed?

  13. jimmy927 commented on Nov 8, 2025

    @jimmy927

    Solved in 2.0.35

    Image
  14. pzgz commented on Nov 23, 2025

    @pzgz

    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

    Image
  15. github-actions commented on Jan 16, 2026

    @github-actions

    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.

  16. moritzWa commented on Jan 24, 2026

    @moritzWa

    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.

  17. Uriel1339 commented on Feb 20, 2026

    @Uriel1339

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

  18. cidoliveira commented on Feb 22, 2026

    @cidoliveira

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

  19. chasel5050 commented on Mar 15, 2026

    @chasel5050

    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?

  20. AAChartModel commented on Jun 1, 2026

    @AAChartModel

    Any solution here? 👀

  21. cidoliveira commented on Jun 1, 2026

    @cidoliveira

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

    Image
  22. AAChartModel commented on Jun 8, 2026

    @AAChartModel

    @cidoliveira Thanks, it works for me now!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions