{"version":"2.1.234","anchor":"every-artifact-asset-action-now-asks-permission-with-its-own","canonical_anchor":"every-artifact-asset-action-now-asks-permission-with-its-own","heading":"Every artifact asset action now asks permission, with its own consent scope","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/every-artifact-asset-action-now-asks-permission-with-its-own","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Every artifact asset action now asks permission, with its own consent scope\n\nUploading, listing, reading and deleting artifact files each ask permission separately, with deletes asking every time.\n\n**What**\n\nUploading, listing, reading and deleting files attached to a published artifact each prompt separately. Upload consent can cover the rest of the session, reading someone else's artifact assets asks once per conversation, and every delete asks on its own. These prompts appear only when asset actions are enabled by `CLAUDE_CODE_ARTIFACT_ASSETS`.\n\n**Details**\n\n- The upload prompt names both the file and the artifact and states whether approving covers the rest of the session.\n- Plan mode and Cowork frame sessions have no place to ask a person, so these actions are denied outright instead of auto-approved.\n- All four prompts set `suppressAlwaysAllowRule`, so no permanent always-allow rule can be created from them.\n- Consent is remembered in app state under keys including `artifactAssetUploadConsentSlugs` and `artifactAssetReadHumanConsentSlugs`.\n\n**Evidence**\n\n`each delete asks separately.`\n\n- Area: Artifacts\n- Names: `CLAUDE_CODE_ARTIFACT_ASSETS`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}