Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.317 ·

Cloud session network relay now limits busy connections and queues the rest

The agent proxy relay now makes new connections wait once too many are busy, and may refuse them with a 429 or 503 error

You'll notice Improvements
JSON All of v2.1.317
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SessionsArea: what it touches
ImprovementsKind: in v2.1.317,
ImprovementsSection of the release

Unclear The default limit, and whether the limit is applied by default, are not stated.

What

In 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.

Now:

  • New connections wait once too many tunnels are busy.
  • 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."
  • CCR_AGENT_PROXY_MAX_BUSY_TUNNELS sets how many busy tunnels are allowed.
  • When opening the relay's link is refused with 429 or 503, Claude Code waits and then tries again instead of retrying at once.
Why

Cloud 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.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe default limit, and whether the limit is applied by default, are not stated.

See this entry in the whole of v2.1.317 →

Feedback