{"version":"2.1.311","anchor":"remote-proxy-requests-for-webfetch-and-websearch-get-a-deadl","canonical_anchor":"remote-proxy-requests-for-webfetch-and-websearch-get-a-deadl","heading":"Web fetches and searches in remote sessions now stop at a deadline","tier":"notice","area":"Sessions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/remote-proxy-requests-for-webfetch-and-websearch-get-a-deadl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Web fetches and searches in remote sessions now stop at a deadline\n\nIn remote sessions, WebFetch and WebSearch requests sent through a proxy now fail with a clear error if they pass a deadline\n\n**Unclear.** It is not stated how long the deadline is by default or whether it can be changed.\n\n**What**\n\nIn 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.\n\nThe 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.\n\n**Why**\n\nA stalled web request in a remote session now fails with a clear message instead of hanging.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}