[BUG] Claude Code desktop ignores permission configurations for WSL projects, requiring approval for every file operation despite proper settings

[nykwil]

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

Issue: Claude Code desktop ignores permission configurations for WSL projects, requiring approval for every file operation despite proper settings
Details tested:

• .claude/settings.local.json with bypass permissions mode doesn't work
• Specific WSL path permissions (//wsl.localhost/Ubuntu/home/nykwil/**) ignored
• Desktop app settings file at C:\Users\admin\AppData\Local\ClaudeCodeExtension\claudecode-settings.json only contains UI preferences
• Both simplified and detailed permission configurations fail
• Issue affects Windows/WSL development workflows
  Impact: Makes WSL development frustrating since every command requires manual approval

What Should Happen?

Permissions settings should be loaded on wsl projects

Error Messages/Logs

Steps to Reproduce

Open a project on a the wsl drive. Enable bypass permissions, do something that requires file read or write, allow prompt shows up.

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

No response

Claude Code Version

Version 1.1.7714 (3bd6f6)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

Claude Desktop for windows

[github-actions]

Found 3 possible duplicate issues:

1. [BUG] Permission patterns not working on Windows/WSL - session-level allow ignored #29574
2. --dangerously-skip-permissions does not bypass Edit permission prompts #36192
3. Edit tool prompts for permission despite bypassPermissions mode + --dangerously-skip-permissions flag #37181

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[yurukusa]

I run Claude Code on WSL2 daily and can share what works:
Root cause: Claude Desktop on Windows accesses WSL paths via \\wsl$\ mount. The permission system likely doesn't resolve WSL paths correctly, so glob patterns in settings.json never match.
Workaround — use CLI instead of Desktop:

npm install -g @anthropic-ai/claude-code
claude --dangerously-skip-permissions

The CLI version runs natively in WSL and resolves paths correctly. Permission settings in ~/.claude/settings.json (WSL-side) work as expected.
If you need Desktop specifically, try setting permissions with the Windows-style path:

{
  "permissions": {
    "allow": [
      "Edit(//wsl$/Ubuntu/**)",
      "Write(//wsl$/Ubuntu/**)",
      "Read(//wsl$/Ubuntu/**)"
    ]
  }
}

Note the //wsl$/ prefix — this is how Windows sees WSL paths. Your distro name may differ (Ubuntu, Debian, etc.).
Alternative — PreToolUse hook auto-approve:

INPUT=$(cat)
FILE=$(echo "$INPUT" | jq -r '.tool_input.file_path // empty')
if echo "$FILE" | grep -qE '^(/home/|/tmp/|/var/)'; then
    echo '{"decision":"approve"}'
fi
exit 0

This auto-approves file operations on standard WSL paths regardless of how Desktop resolves them.

[nykwil]

This bug is specifically about Claude code desktop, there are reasons to use Claude code desktop over the cli.

…

On Sat, Mar 21, 2026, 12:40 p.m. ゆる草 ***@***.***> wrote: *yurukusa* left a comment (anthropics/claude-code#37192) <#37192 (comment)> I run Claude Code on WSL2 daily and can share what works: *Root cause:* Claude Desktop on Windows accesses WSL paths via \\wsl$\ mount. The permission system likely doesn't resolve WSL paths correctly, so glob patterns in settings.json never match. *Workaround — use CLI instead of Desktop:* npm install -g @anthropic-ai/claude-code claude --dangerously-skip-permissions The CLI version runs natively in WSL and resolves paths correctly. Permission settings in ~/.claude/settings.json (WSL-side) work as expected. *If you need Desktop specifically*, try setting permissions with the Windows-style path: { "permissions": { "allow": [ "Edit(//wsl$/Ubuntu/**)", "Write(//wsl$/Ubuntu/**)", "Read(//wsl$/Ubuntu/**)" ] } } Note the //wsl$/ prefix — this is how Windows sees WSL paths. Your distro name may differ (Ubuntu, Debian, etc.). *Alternative — PreToolUse hook auto-approve:* INPUT=$(cat) FILE=$(echo "$INPUT" | jq -r '.tool_input.file_path // empty')if echo "$FILE" | grep -qE '^(/home/|/tmp/|/var/)'; then echo '{"decision":"approve"}'fiexit 0 This auto-approves file operations on standard WSL paths regardless of how Desktop resolves them. — Reply to this email directly, view it on GitHub <#37192?email_source=notifications&email_token=AAHU46DT4FB7XEDV2JAYSND4R3V3LA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJQGQYTENBRGMZKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4104124132>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHU46APVENIMSQUSWDFG5T4R3V3LAVCNFSM6AAAAACW2GGWNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCMBUGEZDIMJTGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[ddarbyson]

Similar reported bug - #11380 (comment)

Seems to be recent as of the last week or so.

[goodspeed-apps]

Same issue happening here for me. I'm getting prompted every 5-10 seconds to approve an edit or write, even with permissions wide open.

[cbornBerlin]

How can this still be open and not assigned!? Claude on Windows Desktop with WSL unusable now since 3 days. It doesn't even recognize "allow for this session" acceptances. This needs to be fixed ASAP! @bcherny

[guillaumemaurino]

+1 Please fix ASAP !