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 \??\ device paths recognised

You'll notice
Useful2 Signal1
Windows

Windows object-manager paths are now recognised as device paths and handled like the other odd forms.

What

Path canonicalisation and the network-path check previously matched only the \\?\ and \\.\ device prefixes. They now also match the \??\ object-manager form, including after Windows normalisation of paths containing ??, so those paths skip canonicalisation and are treated as device paths.

Evidence

e1c = /^[\\/]\?\?[\\/]/;

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 →