{"version":"2.1.302","anchor":"artifact-stale-version-refusals-now-tell-the-model-to-merge","canonical_anchor":"artifact-stale-version-refusals-now-tell-the-model-to-merge","heading":"Artifact conflicts now tell Claude to merge with Edit or Write and resend","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/artifact-stale-version-refusals-now-tell-the-model-to-merge","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Artifact conflicts now tell Claude to merge with Edit or Write and resend\n\nWhen a newer artifact version blocks a publish, Claude is told to copy the live lines into its file with Edit or Write, then resend\n\n**What**\n\nAn artifact is a document or page that Claude publishes for you. When Claude tries to publish edits but a newer version of the artifact is already live, the publish is refused. The message Claude gets now tells it to carry the live version's lines into its file itself with Edit or Write, then send the same publish again. Before, it was told to merge its edits onto the live source and publish again.\n\nThere are also new fixed messages for when Claude sends the same changes again without merging, such as \"Not published: Claude sent its changes again over the same file after a newer version of the artifact turned them away.\"\n\n**Why**\n\nThis changes how Claude recovers when someone else has updated an artifact first, so it merges the newer content instead of resending the same refused changes.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}