You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
New FeaturesKind: in v2.1.234,
New FeaturesSection of the release
What
Uploading, 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.
Details
The upload prompt names both the file and the artifact and states whether approving covers the rest of the session.
Plan mode and Cowork frame sessions have no place to ask a person, so these actions are denied outright instead of auto-approved.
All four prompts set suppressAlwaysAllowRule, so no permanent always-allow rule can be created from them.
Consent is remembered in app state under keys including artifactAssetUploadConsentSlugs and artifactAssetReadHumanConsentSlugs.
Evidence
each delete asks separately.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
