Windows: permissions.allow path patterns don't work for scoping Edit/Write to specific directories

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Problem

On Windows, specifying directory-scoped permission rules in settings.json does not work. Neither backslash nor forward slash path patterns are matched.

Attempted patterns (both fail):

"Edit(C:\\Users\\user\\Documents\\projects/**)"
"Edit(C:/Users/user/Documents/projects/**)"

When these rules are set, the permission dialog still appears for files within those directories, indicating the pattern is not being matched.

Expected Behavior

Path-scoped rules like Edit(C:\Users\user\Documents\projects/**) should auto-allow Edit/Write operations only within that directory tree — without requiring defaultMode: bypassPermissions or a global wildcard Edit(*).

Current Workaround

Forced to use defaultMode: acceptEdits with Edit(*) (allows all paths) since path-scoped rules don't function on Windows.

Environment

• OS: Windows 11
• Claude Code: desktop app

Proposed Solution

Fix the path pattern matching in permissions.allow rules to support Windows absolute paths. Both backslash (C:\\Users\\...\\**) and forward slash (C:/Users/.../**) formats should be recognized when evaluating Edit/Write permissions, so users can scope permissions to specific directories without needing a global wildcard or bypassPermissions mode.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_