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.233 Home All releases ←olderv2.1.232 v2.1.234newer→
Claude Code v2.1.233

Windows suspicious-path detection covers flags and NT device paths

You'll notice
Useful2 Signal2
Windows

On Windows, risky paths hidden inside --flag=value arguments or NT device paths are now caught.

What

On Windows, the check that spots risky paths in commands now unwraps --flag=value arguments and re-checks the value, and flags NT object paths containing a /??/ segment.

Details
  • A normalizer collapses repeated \??\ prefixes before the check runs.
  • The cygwin-style /c/... to C:\ conversion is now done inline rather than through a helper that was removed.
  • The sandbox path validator now uses the same shared UNC and device-path check as the rest of the detector.
Evidence

DavWWWRoot

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