{"version":"2.1.248","anchor":"agent-proxy-adds-flow-control-with-caps-and-stall-aborts","canonical_anchor":"agent-proxy-adds-flow-control-with-caps-and-stall-aborts","heading":"Agent proxy adds flow control with caps and stall aborts","tier":"internal","area":"Agent Proxy","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/agent-proxy-adds-flow-control-with-caps-and-stall-aborts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Agent proxy adds flow control with caps and stall aborts\n\nThe local agent proxy now pauses or aborts transfers that stall or buffer too much.\n\n**What**\n\nThe 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.\n\n**Details**\n\n- Limits come from the connection's limits object (`receiveHighWater`, `sendPauseAfterPendingBytes`); there is no flag.\n- The proxy reports each facility as enabled only when the corresponding limit is a finite number.\n- Cap breach is logged as \"[agent-proxy] pending buffer cap (\".\n\n**Evidence**\n\n`[agent-proxy] pending buffer cap (`\n\n- Area: Agent Proxy\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}