{"version":"2.1.229","anchor":"artifact-viewer-blocks-downloads-the-page-starts-by-itself","canonical_anchor":"artifact-viewer-blocks-downloads-the-page-starts-by-itself","heading":"Artifact viewer blocks downloads the page starts by itself","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/artifact-viewer-blocks-downloads-the-page-starts-by-itself","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Artifact viewer blocks downloads the page starts by itself\n\nArtifact pages can't start downloads themselves, so Claude is told not to offer plain download links.\n\n**What**\n\nThe Artifact tool description now warns that the viewer sandbox makes any page-initiated download inert, including `<a download>` links pointing at data: or blob: URLs and script-driven saves, so a file must never be offered through a plain link. Handing the viewer a file to save is now listed as a runtime capability to look up in the artifact-capabilities skill.\n\n**Evidence**\n\n`blocks any download the page starts itself`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}