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

Windows device-namespace paths rejected as socket addresses

You'll notice
Useful1 Signal1
Windows

Windows device-namespace paths are now rejected as message socket targets.

What

A uds: or bridge: message target starting with a \??\-style prefix is now rejected with the existing "is not a local socket address" error rather than being passed through to the named-pipe check.

Evidence

is not a local socket address. Use an address from

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