{"version":"2.1.234","anchor":"artifact-asset-actions-get-their-own-fail-closed-message","canonical_anchor":"artifact-asset-actions-get-their-own-fail-closed-message","heading":"Artifact asset actions get their own fail-closed message","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/artifact-asset-actions-get-their-own-fail-closed-message","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Artifact asset actions get their own fail-closed message\n\nFailed artifact asset permission checks now give the right explanation for where they happened.\n\n**What**\n\nWhen a permission check for an artifact action cannot complete, the action is still refused, but the explanation now depends on where it happened: inside the shared cowork frame it keeps the consent-floor wording, and outside it reads as an asset-action message instead of a misleading cowork one.\n\n**Evidence**\n\n`Artifact asset actions fail closed when their permission check cannot complete`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}