{"version":"2.1.317","anchor":"server-cleared-classifier-allow-now-tracked-for-url-fetches","canonical_anchor":"server-cleared-classifier-allow-now-tracked-for-url-fetches","heading":"Web fetches cleared by an automatic check with server approval are now singled out","tier":"internal","area":"Web Fetch","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/server-cleared-classifier-allow-now-tracked-for-url-fetches","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Web fetches cleared by an automatic check with server approval are now singled out\n\nClaude Code can now pick out the web address of a fetch that an automatic permission check allowed and the server marked as cleared\n\n**What**\n\nBefore Claude fetches a web page, a permission check decides whether it may. Claude Code now has a step that picks out the web address when all three of these are true:\n\n- the check allowed the fetch\n\n- the decision came from a classifier, an automatic check rather than you\n\n- the decision was marked as cleared by the server\n\nThis step sits next to a list of web redirect codes: 301, 302, 303, 307 and 308. A site sends one of these codes to point a request at a different address.\n\n**Why**\n\nIt gives Claude Code a way to recognise fetches that were cleared automatically with the server's agreement. It is kept alongside Claude Code's handling of redirects.\n\n- Area: Web Fetch\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}