{"version":"2.1.248","anchor":"artifact-updates-from-an-earlier-conversation-need-a-read-fi","canonical_anchor":"artifact-updates-from-an-earlier-conversation-need-a-read-fi","heading":"Artifact updates from an earlier conversation need a read first","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/artifact-updates-from-an-earlier-conversation-need-a-read-fi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Artifact updates from an earlier conversation need a read first\n\nPublishing to an artifact this conversation never read is refused, and returns the live version.\n\n**What**\n\nThe Artifact tool's instructions now require reading an artifact you only have the URL for before publishing to it. A publish to an artifact this conversation has never read or published is refused, and the refusal returns the current live version so the model can build on it instead of overwriting.\n\n**Details**\n\n- Applies to every session that has the Artifact tool; no setting involved.\n\n**Evidence**\n\n`a publish to an artifact this conversation has not read or published is refused and hands you the live version to build on`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}