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.238 Home All releases olderv2.1.237 v2.1.239newer
Claude Code v2.1.238

Bridge 403s log which system rejected them

Under the hood
Useful2 Signal3
Remote Bridge

An unexplained 403 from the bridge now logs which system rejected it and can be retried instead of dropping the connection.

What

A 403 from the bridge endpoint that is not a recognised rejection now derives a source from the response headers, logs it, and attaches it to the terminal rejection result. A nonOrigin403Transient option lets such a 403 be retried rather than ending the connection.

Evidence

[code-session] /bridge 403 source=

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