Bash permission pattern with wildcard not matching commands with redirects

[snelling-a]

Description

Bash permission patterns using wildcards (*) are not matching commands that include shell redirects like 2>&1, even though they should based on prefix matching logic.

Environment

• Claude Code version: 2.0.59
• Platform: macOS (Darwin 24.6.0)

Configuration

In ~/.claude/settings.json:

{
  "permissions": {
    "allow": [
      "Bash(npm run test*)",
      ...
    ]
  }
}

Expected Behavior

The pattern Bash(npm run test*) should match:

• npm run test
• npm run test 2>&1
• npm run test:unit

Since * is a wildcard that should match any characters after npm run test.

Actual Behavior

Claude Code prompts for permission when running npm run test 2>&1, even though the pattern Bash(npm run test*) is in the allow list.

Notes

• Version 1.0.123 changelog states: "Bash permission rules now support output redirections when matching (e.g., Bash(python:*) matches python script.py > output.txt)"
• This suggests redirects should be handled, but they don't appear to be working with 2>&1
• The piped version npm run test 2>&1 | head -200 also doesn't match, which may be expected behavior due to shell operator security (preventing safe-cmd && malicious-cmd bypasses), but the non-piped redirect case should work

[github-actions]

---

Found 3 possible duplicate issues:

1. Stderr Redirection Causing Unexpected Behavior in Command Execution #4797
2. Permission pattern Bash(gh pr view :*) fails to match commands with --json flag #11150
3. Permission Pattern Matching Fails for PHP Commands with Complex Arguments #5503

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

[github-actions]

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

[mimor]

I'm also running into this issue, but on Linux.

Attempted Workaround

Adding the following to CLAUDE.md:

**IMPORTANT: Do NOT use redirects like `2>/dev/null` in bash commands - they break auto-approve pattern matching.**

This has mixed results - Claude sometimes still adds redirects despite the instruction.

Environment

• Claude Code version: 2.0.76
• OS: Linux 6.18.3-arch1-1 (Arch Linux, x86_64)
• Node.js: v25.2.1
• Shell: bash

Reproduction

1. Add Bash(glab issue view:*) to permissions.allow in settings.json
2. Run a slash command that triggers glab issue view 123 -R repo 2>/dev/null
3. Claude prompts for permission despite the pattern matching the command prefix

Expected

Pattern Bash(glab issue view:*) should match glab issue view 123 -R repo 2>/dev/null

Actual

Permission prompt appears, breaking automated workflows.