{"version":"2.1.321","anchor":"artifact-write-refusal-messages","canonical_anchor":"artifact-write-refusal-messages","heading":"Clearer messages when an artifact can't be written","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/artifact-write-refusal-messages","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Clearer messages when an artifact can't be written\n\nClaude Code now tells the model why an artifact write was refused, not to retry it, and to publish under project\/ instead\n\n**What**\n\nClaude Code now has specific messages for when writing to an artifact is refused. They cover:\n\n- documents that are only a page\n\n- artifacts that keep their content in files under `project\/` rather than in their database\n\n- refusals it does not recognise\n\nThe messages tell the model not to retry the write, and to publish under `project\/` instead.\n\n**Why**\n\nThe model is steered away from repeating a write that will keep failing.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}