{"version":"2.1.317","anchor":"agent-proxy-limits-busy-tunnels-and-queues-extra-connects","canonical_anchor":"agent-proxy-limits-busy-tunnels-and-queues-extra-connects","heading":"Cloud session network relay now limits busy connections and queues the rest","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/agent-proxy-limits-busy-tunnels-and-queues-extra-connects","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Cloud session network relay now limits busy connections and queues the rest\n\nThe agent proxy relay now makes new connections wait once too many are busy, and may refuse them with a 429 or 503 error\n\n**Unclear.** The default limit, and whether the limit is applied by default, are not stated.\n\n**What**\n\nIn cloud sessions, network traffic goes through a relay called the agent proxy. Each connection through it is a tunnel. Before, every new connection was opened right away, with a fixed number of retries.\n\nNow:\n\n- New connections wait once too many tunnels are busy.\n\n- Connections can be refused with a 429 or 503 error and a message: \"Run fewer downloads or requests at once, or close idle connections, then retry.\"\n\n- `CCR_AGENT_PROXY_MAX_BUSY_TUNNELS` sets how many busy tunnels are allowed.\n\n- When opening the relay's link is refused with 429 or 503, Claude Code waits and then tries again instead of retrying at once.\n\n**Why**\n\nCloud sessions that run many downloads or requests in parallel may now see them queue or fail with 429 errors. Running fewer at once avoids this.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}