bypassPermissions mode still prompts for Edit/Write on UNC paths (Windows)

Open 💬 4 comments Opened Apr 1, 2026 by mklod

Description

On Windows 10, bypassPermissions mode does not auto-approve Edit/Write tool calls when the working directory or file paths use UNC paths (\server\share\...). Claude Code always shows the "Do you want to make this edit?" confirmation prompt, even though the file is inside the current working directory.

Repro

  1. Windows 10, Claude Code latest, Git Bash shell
  2. Global settings.json has "defaultMode": "bypassPermissions" and "skipDangerousModePermissionPrompt": true
  3. Launch CC from a UNC path: cd //server/share/project && claude --dangerously-skip-permissions
  4. Ask CC to edit any file in the project

Expected: Edit proceeds without prompting (bypass mode)
Actual: "Do you want to make this edit to file.html?" prompt appears every time

What was tried (none worked)

  • Adding UNC path to additionalDirectories (both \\server\share and //server/share formats)
  • Adding "defaultMode": "bypassPermissions" at project level in .claude/settings.local.json
  • PreToolUse hook returning {"decision":"approve"} — hook fires and returns approve correctly, but CC still prompts
  • Fresh session (not resumed)
  • Removing local symlinks that previously pointed to the UNC path

Debug info

PreToolUse hook logging confirms:

  • permission_mode is "bypassPermissions"
  • cwd is \\MURKYSERVER\murky\PROJECTS\gram1-web
  • file_path is \\MURKYSERVER\murky\PROJECTS\gram1-web\site\product.html (inside cwd)
  • The prompt still appears

Workaround

Using a mapped drive letter (e.g., L:\PROJECTS\project) instead of a UNC path works correctly — bypassPermissions is respected and edits proceed without prompting.

Environment

  • Windows 10 Home 10.0.19045
  • Shell: Git Bash
  • UNC path via SMB to local NAS
  • Claude Code latest stable channel

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗