Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.260 ·

Artifact tool results flag cross-artifact copied content as untrusted

New schema fields hint at cross-artifact asset copying, but nothing uses them yet.

TierUnder the hoodhow much it should matter to you
Useful1my rating, 1 to 5
Signal3worth watching, 1 to 5
AreaArtifactswhat it touches
KindInternal Changesin v2.1.260,
Group of 3 Under the hood Nothing to try yet No documentation found

New schema fields hint at cross-artifact asset copying, but nothing uses them yet.

The asset-list schema (ge) gains a cowritten boolean field, and a new schema (Te) validates { assets: [...].extend({ from_id: ... }) } capped at a maximum count, laying groundwork for attributing assets copied from another artifact. The artifact file_list and file_read tool responses can now include a from_type flag when the served content type was determined by the artifact's declared type rather than sniffed.

Tool-result messages for asset_list, asset_read, and file_read now surface the cowritten field (and, for file listings, from_type), and the returned text explicitly warns the model to treat such assets or files as untrusted data when a co-writer or an Artifact type's publisher, rather than the user, produced them.

Read from
Names in the bundleasset_copy

See this entry in the whole of v2.1.260 →

Feedback