{"version":"2.1.285","anchor":"web-fetch-error-categories","canonical_anchor":"web-fetch-error-categories","heading":"WebFetch reports rate-limited domain checks and applies read_file rules to artifacts","tier":"notice","area":"Web Fetch","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/web-fetch-error-categories","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### WebFetch reports rate-limited domain checks and applies read_file rules to artifacts\n\nWebFetch now says when its domain safety check is rate-limited, sorts fetch failures by cause, and checks read_file rules for artifact links\n\n**Unclear.** It is not clear whether these categories are shown to you or only used in usage reporting.\n\n**What**\n\nWebFetch is the tool Claude uses to read a web page. Before fetching, it checks whether the domain is safe.\n\n- When that check is refused for too many requests (HTTP 429), the error code is now `ERATELIMIT_PREFLIGHT` and the message says the domain \"is temporarily rate-limited (too many domain checks from this network)\". Before, it was the generic \"Unable to verify if domain\" message.\n\n- Fetch failures are now sorted into kinds. Proxy problems: transport, bad response, rate limited, unavailable, rejected. Problems with the target: `invalid_input`, `url_not_allowed` and others.\n\n- Fetching an artifact link now also checks permission rules for the `read_file` action, using the artifact's file path. Before, only the read action was checked.\n\n**Why**\n\nIf you hit the rate limit, the message now says the domain check was rate-limited instead of looking like a network fault. Rules that deny or ask before reading files now also apply when Claude fetches an artifact link.\n\n- Area: Web Fetch\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}