{"version":"2.1.323","anchor":"artifact-publish-refusal-text-for-unreadable-existing-files","canonical_anchor":"artifact-publish-refusal-text-for-unreadable-existing-files","heading":"Publishing an artifact won't overwrite files Claude can't read unless you ask","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/artifact-publish-refusal-text-for-unreadable-existing-files","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Publishing an artifact won't overwrite files Claude can't read unless you ask\n\nWhen an artifact publish would replace files Claude can't read, Claude now stops and tells you, and forces the overwrite only if you ask\n\n**What**\n\nAn artifact is a set of files Claude Code publishes for you. Some files may already be published at a path Claude is about to write to, and Claude may be unable to read them. In that case Claude Code now tells the model it must not replace or remove those files. Instead the model should:\n\n- Tell you about the files it can't read.\n\n- Publish again without those paths, or at other paths.\n\n- Publish with `force:true` only if you explicitly ask.\n\nThe message also warns that `force:true` overwrites any newer edit to the other files the same publish writes or removes.\n\n**Why**\n\nFiles you edited yourself are no longer silently overwritten by Claude when it republishes an artifact.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}