Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.321 ·

Permission rules ending in (*) or () are matched differently

Rules written as a tool name followed by (*) or () are read as covering the whole tool, without the earlier allow-only check

You'll notice Improvements
JSON All of v2.1.321
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
PermissionsArea: what it touches
ImprovementsKind: in v2.1.321,
ImprovementsSection of the release

Unclear It is unclear whether deny and ask rules written with (*) or () are now also treated as covering the whole tool.

What

Permission rules tell Claude Code which tools it may use without asking. A rule written as a tool name followed by (*) or () is read as a rule for the whole tool.

Before, Claude Code read rules this way only when they were allow rules and an extra internal check passed. The code that does this no longer looks at what kind of rule it is or at that extra check.

Why

If you use rules written with (*) or (), the way they are matched may differ from before.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is unclear whether deny and ask rules written with `(*)` or `()` are now also treated as covering the whole tool.

See this entry in the whole of v2.1.321 →

Feedback