I’m one of those people who actually enjoys finegrain control over every piece of code. So approving (or rather disapproving with instructions) every single edit is my stick. In fact that’s the main reason I haven’t jumped ship to Codex yet.
What I do not enjoy is hand approve every fricking grep, find, cat, head, git log, wc (whatever that is…)
I’ve experimented so much with .claude/settings.json permissions.allow[] and its genuinely hillarious how many times agent says “Bash(grep *) is wrong, must use colon Bash(grep:*)” and the next says the opposite.
There’s no settings.local.json overriding it. Neither in project folder nor in ~/Users/user/.claude – I tried removing settings files altogether and reset with /fewer-permissions-prompts to no avail. I tried adding bash commands to permissions with their flags individually (-rn -r etc.). No change. Opus 4.5, 4.6 and 4.7 all saying the configs look correct and I should not be prompted with those.
Funny how they like to claim during testing “Nice, I did not prompt you, must be working now!” 1 second after prompting me with grep.
Obviously I restarted the claude session after every change. My
Claude.md
is minimal. No MCP and only skill installed is frontend-design.
When prompted with grep (or find etc.) I only see “Yes” and “No”, but not “Yes, allow always”
I swear it wasnt like this in the past. Is that just Anthropic fumbling again or am I missing something? Oh please let me be missing something.
I’m using Ghostty on macOS Sequoia.
submitted by
/u/katerlouis
Originally posted by u/katerlouis on r/ClaudeCode
You must log in or # to comment.