{"version":"2.1.295","anchor":"artifact-share-and-watch-ask-unconditionally-publish-guards","canonical_anchor":"artifact-share-and-watch-ask-unconditionally-publish-guards","heading":"Artifact sharing always asks through the approval card; publish checks failed edits","tier":"notice","area":"Artifacts","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/artifact-share-and-watch-ask-unconditionally-publish-guards","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Artifact sharing always asks through the approval card; publish checks failed edits\n\nSharing, watching or uploading an artifact always uses the approval card, and publish refuses if an earlier edit in the same reply failed\n\n**What**\n\nWhen Claude wants to share, watch or upload an artifact, or set up a standing job for one, Claude Code now always asks for your approval through its approval card. Before, a check decided whether that card was used, with a plain permission prompt as the fallback. That fallback is gone.\n\nPublishing an artifact now also refuses to go ahead when an Edit or Write that Claude sent earlier in the same reply failed. Claude Code reports that the edit did not apply and that nothing was published.\n\n**Why**\n\nEvery share now goes through the same approval flow. The publish check stops a half-finished version of an artifact from going live when one of its edits did not land.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}