Source Intelligence
Follow Discord

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.221 Home All releases ←olderv2.1.220 v2.1.222newer→
Claude Code v2.1.221

Deny rules are checked against every form of a path

You'll notice
Useful4 Signal0
Permissions

Your deny rules now block a path even when it's written a different way.

What

A deny rule now matches even when the path is written in a form other than the one that got resolved.

Details
  • the deny lookup iterates over the path's variants and returns the first matching rule, instead of testing only the single resolved path
  • the drive-relative rejection message now names the original argument when one is available
  • drive-relative paths still require manual approval because they resolve against the per-drive current directory
Evidence

is drive-relative (resolves against the per-drive current directory, which cannot be statically validated) and requires manual approval

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

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.221 →