Inside the fetch subagent, saved binary downloads are reported without any file path.
What's wrong with this entry?
When a fetch saves binary content to disk from inside the web-fetch subagent, the appended note now tells the subagent it cannot open files and must not include any file path in its report. The ordinary caller path keeps the existing note naming the saved path.
- Only applies on the web-fetch agent path, which is off by default in this build.
You cannot open files here, and the harness gives the caller the path itself — say that the file was saved, but do not put any file path in your 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