Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.221 ·

Windows PowerShell permission checks consider every quote interpretation

On Windows, cleverly quoted shell paths can no longer sneak past your deny rules.

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

Path and command analysis for the Bash tool on Windows is now run over several possible readings of the same string instead of one unquoted spelling, closing gaps where quoting could hide a path from a deny rule.

Details
  • Deny-rule matching, redirection target collection, symlink and executable stem resolution, and dangerous-path detection all run across a variant set.
  • Variants are the raw string plus three quote-stripping/unquoting passes covering curly quotes and backtick escapes, plus the text following a :: stream suffix.
  • Anything containing a quote character that still cannot be resolved statically now falls through to manual approval rather than being allowed silently.
  • Windows only.
Evidence

Paths containing quote characters cannot be statically validated and require manual approval

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.221 →

Feedback