AIToday
Large Language ModelsAI Coding AssistantsZenn AI/MLPublished: Nov 21, 2026, 04:00 JST

Claude Code 2.1.328 warns on bad permission rules, but lowercase bash(git *) stays silent

Send on LINE
Claude Code 2.1.328 warns on bad permission rules, but lowercase bash(git *) stays silent

3 Key Points

  1. What happened

    Testing on 2.1.328 with Haiku, the author found malformed rules like Bash(git with no closing bracket now trigger a warning, but a lowercase bash(git *) gives no warning and never runs—three out of three attempts failed.

  2. Why it matters

    A rule that looks correct and produces no warning is the harder failure to catch, and the warning appears as a single line on standard error while execution finishes normally, so cron jobs logging only standard output may miss it entirely.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Context & Analysis

The author had previously documented that a permission rule missing its closing bracket in Claude Code's --allowedTools passed without comment. The 2.1.326 release notes said a warning was added, so the same tests were rerun on 2.1.328 with the Haiku model, and the result was only a partial fix.

Rules with broken bracket shapes—no closing bracket, a space before the bracket, or extra characters after it—now produce a warning that even mentions checking for a missing closing bracket or space. A correctly formed Bash(git *) rule gave no warning and ran in all three attempts, and Bash(echo a,b) also worked all three times.

The gap sits with rules that are well-formed but wrong in another way. Writing the tool name in lowercase as bash(git *) draws no warning because the shape is valid, yet nothing is granted—three out of three runs failed—which the author notes is harder to notice than a malformed rule. The author also checked 31 scheduled-run logs that capture standard error in the same file and found zero warnings, and searched 12 local config files for lowercase tool names and found none. Running claude doctor from the CLI did not surface broken skills or mismatched hook conditions; the author says those appear in the interactive /doctor or /status views instead.

FAQ
Does the new warning catch every broken permission rule?
No. In testing on 2.1.328, malformed brackets and extra characters triggered a warning, but a lowercase tool name like bash(git *) produced no warning at all.
What actually happens when I write bash(git *) in lowercase?
Nothing is permitted—the command failed to run in all three attempts—and no warning is shown, so it is easy to assume the rule worked.
Why might I miss the warning even when it appears?
The warning is a single line on standard error while execution continues and ends normally, so scheduled runs that only log standard output will not record it.
Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleUS tech giants shift AI race to agentic action, led by Amazon and Google