Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.260 ·

Artifact tool results flag cross-artifact copied content as untrusted

Artifact file responses can now flag when content type was locked by the artifact's type.

Group of 3 You'll notice No documentation found Internal Changes
JSON All of v2.1.260
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
Internal ChangesKind: in v2.1.260,
ImprovementsSection of the release

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 bundlefrom_type

See this entry in the whole of v2.1.260 →

Feedback