Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.246 Home All releases olderv2.1.245 v2.1.247newer
Claude Code v2.1.246

Warning when a Bash allow rule wildcards the subcommand slot

You'll notice
Useful4 Signal3
Permissions

Adding an allow rule like Bash(git *) now warns the wildcard also auto-approves dangerous options.

What

Adding an allow rule such as Bash(git ) now warns that the wildcard also matches options placed at that position and approves them without prompting, and suggests putting the after the subcommand instead. git is called out because options like -c and --exec-path can run arbitrary commands.

Details
  • This is a warning only. The rule is still accepted and saved.
  • It fires during allow-rule validation, on the allow path only.
Evidence

For git, options such as -c and --exec-path can run arbitrary commands.

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.246 →