[BUG] Bash permission pattern with >> redirect not auto-approving from settings.local.json

Resolved 💬 3 comments Opened Mar 5, 2026 by abhishekthamman Closed Mar 9, 2026

Preflight Checklist

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

What's Wrong?

Bash permission patterns containing >> (append
redirect) in .claude/settings.local.json do not
auto-approve, while other Bash patterns in the same
file work correctly.

What Should Happen?

Expected: Both auto-approve since both are in the
allow list with the same glob syntax.

Actual: Patterns with >> redirect always prompt.
Patterns without shell operators work fine.

Error Messages/Logs

Steps to Reproduce

  1. Add to .claude/settings.local.json allow list:
  • "Bash(curl hooks.slack.com)"
  • "Bash(echo >> audit*)"
  1. Run curl -s -X POST "https://hooks.slack.com/..." →

auto-approves ✅

  1. Run echo '{"key":"value"}' >>

/path/audit/audit.jsonl → prompts for approval ❌

Environment: Claude Code CLI, macOS Darwin 25.1.0,
Vertex AI

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.68

Platform

Google Vertex AI

Operating System

macOS

Terminal/Shell

iTerm2

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗