Follow Discord
Sweep 12 Nov 2026 · 23:00Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.323 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.323 ·

File path permission rules handle negated patterns and ** differently

Path permission rules now let a negated !** pattern cover everything below its folder, and allow rules written as negations are checked last

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

Permission rules are entries in your settings that allow or deny Claude Code access to files by path. They can use wildcard patterns, such as **, which stands for any number of nested folders. A pattern starting with ! is a negation, meaning "everything except this". Claude Code now prepares these rules differently:

  • A negated pattern such as !** now matches everything below the folder it starts from.
  • Allow rules that are negations are now placed last when rules are checked.
  • An error while matching a rule against ignore patterns is now caught and handled, instead of breaking the check.
  • A rule that cannot be read is no longer treated as matching the literal path it spells out.

The new handling falls back to on when the server sends nothing.

Why

This changes which file paths are allowed or denied. If you use negated patterns or ** in your permission rules, check that they still allow and deny what you expect.

Read from
Feature flag
tengu_vivid_wreath Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.323: on

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.323. It isn't a statement about your account. What a flag value here can and cannot tell you

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_vivid_wreath

See this entry in the whole of v2.1.323 →

Feedback