{"version":"2.1.232","anchor":"the-artifact-self-update-permission-is-now-called-artifact","canonical_anchor":"the-artifact-self-update-permission-is-now-called-artifact","heading":"The artifact self-update permission is now called artifact","tier":"use","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/the-artifact-self-update-permission-is-now-called-artifact","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### The artifact self-update permission is now called `artifact`\n\nSelf-updating artifact pages now declare an `artifact` capability, though the old `self` spelling still works.\n\n**What**\n\nPages built by the design canvas, whiteboard and artifact editor that can publish changes back to themselves now declare `capabilities: {artifact: {}}`; the older spelling `self` is still accepted. Declaring both with different configs is rejected.\n\n**Details**\n\n- At runtime the page looks up `window.claude.artifact` and falls back to `window.claude.self`; permission checks ask for `artifact` when it is present.\n- Skill and template guidance now says to declare exactly one spelling, and the whiteboard's Send to Claude instructions ask for `artifact: {}`.\n- The failure wording changed too: without the capability the canvas no longer \"opens read-only\", it simply cannot keep changes and Save is refused.\n\n**Evidence**\n\n`capabilities: {artifact: {}, downloads: {}}`, ``capabilities declares both `artifact` and `self` \u2014 two ``, ``legacy spelling `self```\n\n- Area: Artifacts\n- Names: `capabilities`, `artifact`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}