{"version":"2.1.311","anchor":"webfetch-gets-a-maxwords-value-from-tengu-humming-waffle","canonical_anchor":"webfetch-gets-a-maxwords-value-from-tengu-humming-waffle","heading":"WebFetch summaries can take a word limit set from the server","tier":"internal","area":"WebFetch","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/webfetch-gets-a-maxwords-value-from-tengu-humming-waffle","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### WebFetch summaries can take a word limit set from the server\n\nWebFetch now passes a word limit, set remotely and 0 when the server sends nothing, to the step that summarises a fetched page\n\n**Unclear.** It is not clear whether the fallback of 0 means no limit.\n\n**What**\n\nWebFetch is the tool Claude uses to read a web page; the page content is then summarised before Claude sees it. That summarising step is now given a maximum word count. The value comes from a remote setting, and when the server sends nothing it falls back to 0.\n\n**Why**\n\nThis could cap how long fetched-page summaries are.\n\n- Flag `tengu_humming_waffle`: Not enough to say (read for one account on one subscription tier against v2.1.311; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: WebFetch\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}