{"version":"2.1.287","anchor":"artifact-tool-svg-images-can-be-copied-between-artifacts","canonical_anchor":"artifact-tool-svg-images-can-be-copied-between-artifacts","heading":"SVG images now copy with an artifact publish","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/artifact-tool-svg-images-can-be-copied-between-artifacts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### SVG images now copy with an artifact publish\n\nArtifact tool guidance now says SVG images copy when you publish, while HTML and XML documents still do not\n\n**Unclear.** It is not clear what decides when the \"writes still work\" wording is dropped.\n\n**What**\n\nClaude Code's instructions to the model for its artifact tool have changed in two places:\n\n- Copying files: SVG images are now listed among the files that copy along with a publish, together with script, style, data, font and other image files. HTML and XML documents still do not copy. Before, SVG was grouped with HTML and XML as not copying.\n\n- Network off: the error shown when a read fails because network access is off no longer ends with \"writes still work\" in some cases.\n\n**Why**\n\nThis changes what Claude expects to happen to SVG images when it publishes, so it should no longer work around them as if they would be left behind.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}