Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.319 ·

Wildcard Bash allow rules no longer approve compound or unusual commands

Wildcard Bash permission rules now get an extra check, so a compound or unusual command no longer matches them

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

Unclear Which wildcard rules get the extra check is not stated.

What

Permission rules decide which commands Claude Code may run without asking you. A wildcard rule uses * to match many commands at once. Before, a command that fit the wildcard pattern matched the rule straight away.

Now Claude Code also splits the command into its separate words in two ways and compares the results. If they disagree, for example because of unusual quoting or because the command chains several commands together, the wildcard rule does not match. The extra check applies only to certain rules, and only to commands under a length limit.

Why

A wildcard allow rule can now approve fewer commands automatically, so a command dressed up to look like an allowed one gets to the usual permission check instead.

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 doubtWhich wildcard rules get the extra check is not stated.

See this entry in the whole of v2.1.319 →

Feedback