{"version":"2.1.268","anchor":"webfetch-requests-now-enforce-a-deadlinetimeout","canonical_anchor":"webfetch-requests-now-enforce-a-deadlinetimeout","heading":"WebFetch requests now enforce a deadline\/timeout","tier":"use","area":"WebFetch","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/webfetch-requests-now-enforce-a-deadlinetimeout","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### WebFetch requests now enforce a deadline\/timeout\n\nWebFetch requests now enforce a timeout and fail with a clear deadline error if exceeded\n\n**What**\n\nWebFetch requests now have a deadline enforced on them. The deadline comes from the `CLAUDE_CODE_WEBFETCH_DEADLINE_MS` environment variable if it's set, otherwise from a remote configuration value, capped at a maximum. If a fetch doesn't complete within that time, it's aborted and fails with a \"Fetch did not complete within the deadline\" error.\n\n**Why**\n\nThis prevents a WebFetch call from hanging indefinitely, giving a clear, specific error when a fetch takes too long instead of leaving it to stall.\n\n- Area: WebFetch\n- Names: `CLAUDE_CODE_WEBFETCH_DEADLINE_MS`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}