Follow Discord
Sweep 29 Sep 2026 · 18:10Z Build v2.1.285 506 read Stable v2.1.280 Latest v2.1.285 Next v2.1.285 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.285 ·

WebFetch reports rate-limited domain checks and applies read_file rules to artifacts

WebFetch now says when its domain safety check is rate-limited, sorts fetch failures by cause, and checks read_file rules for artifact links

Group of 3 You'll notice Improvements
JSON All of v2.1.285
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Web FetchArea: what it touches
ImprovementsKind: in v2.1.285,
ImprovementsSection of the release

What

WebFetch is the tool Claude uses to read a web page. Before fetching, it checks whether the domain is safe.

  • 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.
  • 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.
  • 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.

Why

If 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.

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 clear whether these categories are shown to you or only used in usage reporting.

See this entry in the whole of v2.1.285 →

Feedback