Read tool prompts for permission despite explicit allow rules in settings.local.json

Description

The Read tool prompts for user permission on files that are explicitly allowed in settings.local.json, while other tools (like Glob) on the same paths work without prompting.

Environment

• Claude Code version: 2.1.50
• OS: Debian Linux (amd64)
• Working directory: /opt/projects/

Configuration

Allow rules exist on both levels:

Global (~/.claude/settings.local.json):

{
  "permissions": {
    "allow": [
      "Read(/home/jens/.claude/*)",
      "Read(/home/jens/.claude/**)",
      "Read(/home/jens/.claude/**/*)"
    ]
  }
}

Project (/opt/projects/.claude/settings.local.json):

{
  "permissions": {
    "allow": [
      "Read(/home/jens/.claude/*)",
      "Read(/home/jens/.claude/**)",
      "Read(/home/jens/.claude/**/*)"
    ]
  }
}

Reproduction steps

1. Configure allow rules for Read(/home/jens/.claude/**) on both global and project level
2. In a conversation, ask Claude to read ~/.claude/CLAUDE.md
3. Claude calls Glob(/home/jens/.claude/**/**) → works without prompting
4. Claude calls Read(/home/jens/.claude/CLAUDE.md) → prompts for permission

Expected behavior

Read should be auto-approved for paths matching the allow rules, just like Glob is.

Actual behavior

Read prompts for user confirmation despite matching allow rules. Glob on the same path pattern works without prompting.

Related issues

• #11285 (regression in v2.0.36, Read tool requires permission despite allow rules)
• #13340 (global/local settings.json allow permissions not respected)
• #6631 / #4467 (permission patterns not enforced for Read/Write)

These were reported months ago but the issue persists in v2.1.50.