{"version":"2.1.321","anchor":"webfetch-errors-on-an-empty-model-answer","canonical_anchor":"webfetch-errors-on-an-empty-model-answer","heading":"Web page fetching now reports a clear error when the reader model gives no answer","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/webfetch-errors-on-an-empty-model-answer","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Web page fetching now reports a clear error when the reader model gives no answer\n\nIf the small model that reads a fetched page returns nothing, `WebFetch` now raises an error saying so and that retrying may work\n\n**What**\n\nThe `WebFetch` tool fetches a web page and has a small, fast model read it. If that model returns nothing, the tool now fails with: \"The small, fast model that reads the content gave no answer. Trying again may work.\" Before, it returned the text \"No response from model\" as if it were a result.\n\n**Why**\n\nThe failure is clearer, and it says plainly that trying again may help.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}