Under the hood
Useful2 Signal2
The local agent proxy now pauses or aborts transfers that stall or buffer too much.
What's wrong with this entry?
Anonymous. No account, no email.
What
The local agent proxy now counts queued bytes in each direction, pauses the client socket once pending upload bytes pass a high-water mark and resumes on drain, aborts a request when the pending-buffer cap is exceeded, and aborts when the tunnel accepts no request bytes within a timeout window.
Details
- Limits come from the connection's limits object (
receiveHighWater,sendPauseAfterPendingBytes); there is no flag. - The proxy reports each facility as enabled only when the corresponding limit is a finite number.
- Cap breach is logged as "[agent-proxy] pending buffer cap (".
Evidence
[agent-proxy] pending buffer cap (
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