Source Intelligence

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.221 Home All releases olderv2.1.220 v2.1.222newer

Chrome bridge takes an injected WebSocket factory and closes cleanly

You'll notice
Useful2 Signal0
Chrome & Browser

Fixes the Chrome bridge leaving half-open connections behind when it shuts down.

What

The bridge connector can be handed its socket constructor, and teardown no longer leaves non-open sockets to terminate().

Details
  • Uses a caller-supplied createWebSocket when present, otherwise constructs the ws client itself.
  • On teardown it detaches listeners and then always calls close(), rather than terminating sockets that are not in the OPEN state.
Evidence

chrome_bridge_connection_started

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