You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
SessionsArea: what it touches
ImprovementsKind: in v2.1.311,
ImprovementsSection of the release
Unclear It is not stated how long the deadline is by default or whether it can be changed.
What
In remote sessions, the WebFetch and WebSearch tools send their requests through a proxy, a server that passes them on. Those requests now run against a deadline. When it is reached, the request fails with the error type PROXY_DEADLINE and status 504, with a message saying the proxy had not finished answering in time.
The waits between retries can be cut short by the deadline, and Claude Code stops retrying when too little time is left. A deadline of 0 means there is none. Connection errors are now also recorded for diagnostics.
Why
A stalled web request in a remote session now fails with a clear message instead of hanging.
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 doubtIt is not stated how long the deadline is by default or whether it can be changed.