{"version":"2.1.232","anchor":"webfetch-reports-which-local-files-a-fetch-actually-wrote","canonical_anchor":"webfetch-reports-which-local-files-a-fetch-actually-wrote","heading":"WebFetch reports which local files a fetch actually wrote","tier":"notice","area":"Web Fetch","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/webfetch-reports-which-local-files-a-fetch-actually-wrote","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### WebFetch reports which local files a fetch actually wrote\n\nWeb fetches of non-text content now list exactly which local files they wrote to disk.\n\n**What**\n\nWhen a fetched URL returns non-text content, Claude writes the raw bytes to disk. This release adds a record of those writes and prints it in the transcript as a harness note listing exactly which local files the run produced, with a warning that any other path in the report came from the page text rather than from disk.\n\n**Details**\n\n- The record holds the directories and file paths written, and is threaded from the web-fetch task through the task store, the tool-result plumbing and the fetch cache.\n- A cache hit re-registers the path it previously saved to, so repeat fetches still report their file.\n- If the agent's own structured output already contains a saved-files key, the harness drops it and logs that it did, so the note always comes from the harness and not from the model.\n\n**Evidence**\n\n`[Harness note, not part of the agent's report: `\n\n- Area: Web Fetch\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}