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.
Failed WebSocket upgrades are reported with the reason, not just a status
Under the hood
Useful2Signal2
Internals
Failed WebSocket connections now record why, separating a server rejection from a Cloudflare block.
What's wrong with this entry?
Anonymous. No account, no email.
What
When a WebSocket connection fails to upgrade, the recorded outcome now distinguishes a rejection by the server from one mitigated by Cloudflare, with the HTTP status appended and clamped to 100 to 599. Close reasons for asks that were shown locally but never forwarded are flagged separately.
Evidence
cf_mitigated
Strings lifted out of the shipped bundle, so the claim above can be checked against them.