Windows: Invalid path format in Permission suggestions (//c/mnt/c/ prefix)

Description

On Windows, Claude Code generates invalid path format in Permission suggestions. The path combines Windows drive letter with WSL-style /mnt/c/ prefix, resulting in an unusable path.

Error Message

At startup, the following error appears:

Path C:\mnt\c\Users\kazin\Desktop\mobile_workspace was not found.

Debug Log Evidence

In debug logs, Permission suggestions show:

"Permission suggestions for Bash: [
  {
    "type": "addRules",
    "rules": [
      {
        "toolName": "Read",
        "ruleContent": "//c/mnt/c/Users/kazin/Desktop/**"
      }
    ],
    "behavior": "allow",
    "destination": "localSettings"
  }
]"

Expected Behavior

On Windows, paths should be:

• C:\Users\kazin\Desktop\** (Windows format)
• or //c/Users/kazin/Desktop/** (POSIX-style for Windows)

NOT: //c/mnt/c/Users/kazin/Desktop/** (invalid hybrid format)

Environment

• OS: Windows 11
• Platform: win32
• Claude Code Version: 2.0.50 (npm-global install)
• Node.js: Latest LTS

Configuration Files Status

All configuration files contain correct Windows paths:

• .mcp.json - Correct (C:/Users/kazin/...)
• claude_desktop_config.json - Correct (C:\Users\kazin\...)
• ~/.claude.json - Correct (C:\Users\kazin\...)

The issue appears to be in Claude Code's internal path conversion logic when generating Permission suggestions.

Impact

• Error message displayed at startup
• Functionality appears unaffected (config files are correct)
• Confusing for users

Reproduction Steps

1. Install Claude Code on Windows via npm
2. Run claude in a project directory
3. Observe the "Path was not found" error at startup
4. Check debug logs for malformed ruleContent paths

---
🤖 Generated with Claude Code