{"version":"2.1.232","anchor":"binary-downloads-get-different-wording-inside-the-web-fetch-","canonical_anchor":"binary-downloads-get-different-wording-inside-the-web-fetch-","heading":"Binary downloads get different wording inside the web-fetch agent","tier":"internal","area":"Web Fetch","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/binary-downloads-get-different-wording-inside-the-web-fetch-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Binary downloads get different wording inside the web-fetch agent\n\nInside the fetch subagent, saved binary downloads are reported without any file path.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- Only applies on the web-fetch agent path, which is off by default in this build.\n\n**Evidence**\n\n`You cannot open files here, and the harness gives the caller the path itself \u2014 say that the file was saved, but do not put any file path in your report.`\n\n- Area: Web Fetch\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}