{"version":"2.1.285","anchor":"webfetch-provenance-telemetry-event-names","canonical_anchor":"webfetch-provenance-telemetry-event-names","heading":"Claude Code records why a web page fetch was denied or skipped","tier":"internal","area":"Web Fetch","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/webfetch-provenance-telemetry-event-names","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Claude Code records why a web page fetch was denied or skipped\n\nClaude Code now has named records for each reason a WebFetch source check can be denied, time out or be skipped\n\n**Unclear.** It is not clear whether the web page source check is live.\n\n**What**\n\nWebFetch is the tool Claude uses to read a web page. Claude Code now has a set of named records for how a check on where a fetch comes from turned out. They cover these outcomes:\n\n- Denied\n\n- Timed out\n\n- Skipped because of the current mode\n\n- Skipped because a deny rule applies\n\n- Skipped because the web address is too long\n\n- No question was shown\n\n- A retry was denied\n\nTwo other new records appear too: one for cleaning up task files in managed agents, and one that logs the result of looking up a remote session to attach to, along with where the lookup started.\n\n**Why**\n\nThis suggests a new check or question about where a WebFetch request comes from.\n\n- Area: Web Fetch\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}