{"version":"2.1.310","anchor":"artifact-publish-refuses-capabilities-not-approved-in-this-p","canonical_anchor":"artifact-publish-refuses-capabilities-not-approved-in-this-p","heading":"Publishing an artifact stops if its capabilities were not approved in this session","tier":"notice","area":"Artifacts","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/artifact-publish-refuses-capabilities-not-approved-in-this-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Publishing an artifact stops if its capabilities were not approved in this session\n\nArtifact publishing now refuses capabilities that cannot be confirmed as approved in the current Claude Code process\n\n**Unclear.** Whether this check is always on or controlled by a setting is not stated.\n\n**What**\n\nWhen an artifact is published with extra capabilities, Claude Code now checks that those capabilities were approved in the same running Claude Code process. If it cannot confirm that, nothing is published and the error says to publish again, and that you may be asked to approve them.\n\n**Why**\n\nPublishing an artifact with capabilities may now stop and ask for your approval instead of going through.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}