VS Code: Edit tool prompts for permission despite bypassPermissions mode
Status Closed — not planned
Reported on v2.1.79
Maintainer reply None cached
Activity 6 comments · opened Mar 19, 2026 · closed Apr 19, 2026
Bug Description
Edit tool operations prompt for user permission in VS Code despite bypassPermissions being configured through multiple mechanisms simultaneously.
Environment
- Claude Code version: 2.1.79
- Platform: macOS (Darwin 25.3.0)
- IDE: VS Code with Claude Code extension
- Working directory:
~/.claude(git repo)
Configuration
All three permission bypass mechanisms are enabled:
- VS Code setting:
Claude Code: Allow Dangerously Skip Permissions= enabled - VS Code setting:
Claude Code: Initial Permission Mode=bypassPermissions - settings.json:
"defaultMode": "bypassPermissions"underpermissions
Additionally, Edit is explicitly in the allow list:
"permissions": {
"allow": ["Bash", "Read", "Write", "Edit", "MultiEdit", ...],
"defaultMode": "bypassPermissions"
}
Steps to Reproduce
- Configure all three bypass mechanisms as described above
- Start a new conversation in VS Code
- Have Claude attempt an
Editoperation on any file in the working directory - Result: Permission prompt appears asking user to approve/deny the edit
- Expected: Edit executes without any prompt
Debugging Performed
- Confirmed
settings.jsonis valid JSON with correct schema - Confirmed no project-level
settings.local.jsonoverriding settings - Removed all PreToolUse hooks (including a SecurityValidator hook on Edit) — issue persists
- Upgraded from 2.1.77 to 2.1.79 — issue persists
- Started new conversations after each config change — issue persists
BashandReadtools appear to work without prompting; the issue is specifically withEdit(and possiblyWrite)
Notes
- The permission prompt is the standard Claude Code approval UI, not a hook-generated prompt
- Clicking "Deny" on the prompt produces the standard rejection message: "The user doesn't want to proceed with this tool use"
- This occurs on every Edit attempt, not intermittently
This issue has 6 comments on GitHub. Read the full discussion on GitHub ↗