{"version":"2.1.300","anchor":"webfetch-via-the-ccr-proxy-records-target-failures-and-norma","canonical_anchor":"webfetch-via-the-ccr-proxy-records-target-failures-and-norma","heading":"Web fetches in remote sessions now remember which addresses failed","tier":"notice","area":"WebFetch","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/webfetch-via-the-ccr-proxy-records-target-failures-and-norma","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Web fetches in remote sessions now remember which addresses failed\n\nWhen web fetches go through the remote-session proxy, Claude Code now tidies the address first and records which addresses failed and why\n\n**What**\n\nIn remote sessions, Claude Code fetches web pages through a proxy (a go-between server that makes the request on its behalf). Two things changed on that path:\n\n- Address cleanup: the web address is now cleaned up by a dedicated step. Before, the only change was turning `http:\/\/` into `https:\/\/`.\n\n- Failure record: Claude Code now keeps a note per address. When the proxy reports that the target site failed in one of a known set of ways, a note is stored. When a later fetch of that address succeeds, the note is cleared.\n\nThe `WebFetch` tool's own description did not change in this release.\n\n**Why**\n\nIn practice, Claude Code now tracks which web addresses have recently failed during a remote session. This entry does not cover what Claude Code does with those notes.\n\n- Area: WebFetch\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}