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.222 Home All releases ←olderv2.1.221 v2.1.223newer→
Claude Code v2.1.222

Agent-proxy tunnel now times out waiting for HELLO_ACK

You'll notice
Useful2 Signal0
Elsewhere

A stalled agent proxy tunnel now fails quickly with a clear reason instead of hanging in limbo.

What

A WebSocket tunnel that never gets its protocol v2 negotiation acknowledged now fails fast instead of continuing in an undefined state.

Details
  • Connecting arms a helloAckDeadline; if the server does not acknowledge protocol v2 within the open timeout, negotiation fails with "tunnel protocol v2 negotiation failed" and a reason built from the fragment "no HELLO_ACK within" plus the elapsed limit.
  • An ack carrying an unexpected version is rejected, and the connection is closed with a 502 "Bad Gateway".
  • The deadline is cleared both on receiving HELLO_ACK and on teardown.
  • A new telemetry event agent_proxy_request_v2_not_acked fires on the failure path.
Evidence

requires tunnel protocol v2; the server did not acknowledge the negotiation (, agent_proxy_request_v2_not_acked

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.222 →