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.251 Home All releases ←olderv2.1.250
Claude Code v2.1.251

Proxy failure records now carry the connection target consistently

Under the hood
Useful1 Signal1
Agent Proxy

Proxy failure records now report the connection target consistently across every failure kind.

What

When a tool call goes through the agent proxy and the connection fails, the target host and port is now stored on the connection when it is opened rather than re-parsed from the request line, so every failure kind reports it the same way.

Details
  • Affected failure kinds include websocket errors, direct dial failures and blocked peers.
  • These records are what the proxy's status endpoint returns, which the system prompt already points Claude at when a tool call breaks.
Evidence

GET /__agentproxy/status on this proxy port shows proxy state and recent failures.

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