Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.234 Home All releases ←olderv2.1.233 v2.1.235newer→
Claude Code v2.1.234

Every artifact asset action now asks permission, with its own consent scope

You'll notice
Useful3 Signal3
Artifacts not in their notes

Uploading, listing, reading and deleting artifact files each ask permission separately, with deletes asking every time.

CLAUDE_CODE_ARTIFACT_ASSETS
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.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.234 →