VS Code extension still prompts for file writes despite allowDangerouslySkipPermissions
Resolved 💬 3 comments Opened Mar 25, 2026 by ojhurst Closed Mar 25, 2026
Description
The VS Code extension prompts "Allow write to [filename]?" for file creation even though claudeCode.allowDangerouslySkipPermissions is set to true in VS Code settings and skipDangerousModePermissionPrompt: true is set in ~/.claude/settings.json.
Steps to Reproduce
- Set
"claudeCode.allowDangerouslySkipPermissions": truein VS Code User Settings - Set
"skipDangerousModePermissionPrompt": truein~/.claude/settings.json - Also have
"Write(*)"in the permissions allow list - Ask Claude to create a new file (e.g., a new
.mdfile) - Extension shows a permission prompt: "Allow write to [filename]?" with options: Yes / Yes, allow all edits this session / No
Expected Behavior
File should be created without prompting, since all three permission mechanisms are configured to allow it.
Actual Behavior
A modal prompt appears asking for permission on every new file creation.
Environment
- Machine: MacBook Pro (Mac14,9), Apple M2 Pro, 16 GB RAM
- macOS: 26.3.1 (Build 25D771280a)
- VS Code: 1.112.0 (arm64)
- Claude Code Extension: anthropic.claude-code@2.1.83
- Claude Code CLI: 2.1.83
- The setting has been in place for a long time — this is not a "needs reload" issue
Relevant Settings
VS Code User Settings:
"claudeCode.allowDangerouslySkipPermissions": true
~/.claude/settings.json:
{
"permissions": {
"allow": [
"Bash(*)",
"Edit(*)",
"Write(*)",
"Read(*)",
"Glob(*)",
"Grep(*)",
"WebFetch(*)",
"WebSearch"
]
},
"skipDangerousModePermissionPrompt": true
}
Screenshot
The prompt looks like this:
Allow write to utah-connect-scan.md?
1 Yes
2 Yes, allow all edits this session
3 No
Tell Claude what to do instead
Esc to cancelThis issue has 3 comments on GitHub. Read the full discussion on GitHub ↗