Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.251 ·

Relay checks whether its runtime reports WebSocket backpressure

The relay tests at startup that its runtime reports backpressure, warning if it doesn't.

Under the hood Internal Changes
JSON All of v2.1.251
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Agent ProxyArea: what it touches
Internal ChangesKind: in v2.1.251,
Internal ChangesSection of the release
What

When the agent-proxy relay starts with a reachability probe configured, it opens a loopback WebSocket, pushes enough data that backpressure should register, and verifies the runtime actually reports queued bytes. If it does not, the relay logs a warning and sends telemetry, because the tunnel's upload throttling relies on that number.

Details
  • Runs whenever the relay's startup probe is set, not behind a separate feature flag.
  • Warning states the upload gate cannot engage on that runtime; the relay still starts.
Evidence

WebSocket.bufferedAmount stays 0 with bytes queued: the upload gate cannot engage on this runtime

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

Feedback