Claude Discovery

← All discoveries

Close-up of wooden Scrabble tiles spelling SECURITY, symbolizing cybersecurity and protection.
Photo by Markus Winkler on Pexels
tool

Claude Code 2.1.246 Warns You Before Your Wildcard Bash Rule Backfires

2026-08-27 ยท source:

Claude Code 2.1.246 adds a startup warning for Bash allow rules with a wildcard placed before the subcommand, since those rules also match options inserted before it.

What it is

A Claude Code maintenance release addressing permission-rule clarity and terminal rendering, including an Auto mode tab in `/permissions` for viewing and editing auto mode classifier rules.

What it does

It flags Bash allow rules like `Bash(git * main)` at startup because the wildcard also matches options inserted before the subcommand, which could let an unintended command slip through an allow rule the user thought was narrow. It also fixes fullscreen mode showing a blank transcript after a terminal resize and a severe slowdown when a diff contains one very long line.

Why it matters

Permission wildcards that match more than the author expects are exactly the kind of quiet gap that undermines Claude Code's sandboxing, so surfacing the ambiguity at startup instead of leaving it to be discovered the hard way is a real safety fix.

How to use it

Update to 2.1.246 or later; the warning appears automatically at startup if any configured Bash allow rule has a wildcard positioned before the subcommand, and `/permissions` now has an Auto mode tab for reviewing classifier rules.

Go to source →
claude-codesecuritypermissions