The relay tests at startup that its runtime reports backpressure, warning if it doesn't.
What's wrong with this entry?
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.
- 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.
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.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.239
Agent proxy allowlist narrowed to named Anthropic hosts
Both mention agent proxy
-
v2.1.239
System prompt lists the CLIs already wired up for the agent proxy
Both mention agent proxy
-
v2.1.239
Agent proxy credential placeholders table-driven, PATH search bounded
Both mention agent proxy