Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.265 ·

Reading a first-party artifact's own files can now skip approval

Reading files from a first-party artifact's own file cache no longer always requires approval, and its progress text now says 'read' instead of 'save'

Group of 2 You'll notice Improvements
JSON All of v2.1.265
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
ImprovementsKind: in v2.1.265,
ImprovementsSection of the release

What

Reading files or assets from the user's own artifact can now be exempted from the usual approval prompt when the artifact was made from a published first-party Artifact type, with a new decision-reason message explaining why. There's also a shortcut for resources that were already read or approved earlier under a display name.

The user-facing progress text for these actions was also updated: the read_file action now shows "read " instead of "save file ", and read_asset now shows "read asset " instead of "save asset ". A destination arrow in the progress text is now suppressed when the resolved destination is a default directory.

Why

These file-cache operations are reads, not writes, so treating them as reads both reduces unnecessary approval prompts for trusted first-party artifacts and makes the displayed action text accurately describe what's happening.

See this entry in the whole of v2.1.265 →

Feedback