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 NT object-manager paths now require manual approval

You'll notice
Useful3 Signal2
Windows

Windows NT object-manager paths now require your manual approval like other suspicious path forms.

What

Paths beginning \??\ (the NT object manager namespace, and spellings that normalise to it) are now treated as suspicious. They trigger the same manual-approval ask as other odd Windows path forms, are rejected by the network-path check, and are caught during general path normalization, which previously only recognised the \\?\ device form.

Details
  • The ask text is unchanged: "which contains a suspicious Windows path pattern that requires manual approval", recorded under the circuit breaker name "suspiciousWindowsPath".
  • The file-upload guard used by Claude in Chrome inherits the new check and throws on a "suspicious path spelling".
Evidence

/^[\\/]\?\?[\\/]/

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 →