You'll notice
Useful3 Signal3
Web fetches of non-text content now list exactly which local files they wrote to disk.
What's wrong with this entry?
Anonymous. No account, no email.
What
When 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.
Details
- 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.
- A cache hit re-registers the path it previously saved to, so repeat fetches still report their file.
- 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.
Evidence
[Harness note, not part of the agent's report:
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.239
Data-loss-prevention blocks are marked separately from fetch failures
Both mention fetch
-
v2.1.236
Web fetch agent switch moved into per-host state
Both mention fetch