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.267 ·

Artifact write_db permission prompts now describe file provenance and version-pinned edits to others' artifacts

Permission prompts for writing to artifacts now explain whose file it is and flag version-pinned edits

You'll notice No documentation found Improvements
JSON All of v2.1.267
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.267,
ImprovementsSection of the release
What

When Claude Code asks permission to write to an artifact's underlying storage (write_db), it now classifies the write as one of four cases: cowritten, from_type, someone_else, or unknown, based on who owns the file. The permission prompt can now be prepended with a description of the file, such as saving a file as a given name or saving a named file to a given location.

It also separately calls out a version-pinned write to someone else's artifact (an edit that targets a specific saved version rather than the latest one): this kind of write always asks for permission on its own, and approving it only covers that one write, until the current conversation has read that artifact's data.

Why

This makes permission prompts for artifact writes more informative about whose file is being changed, and adds an extra safeguard around version-pinned edits to other people's artifacts so approval doesn't inadvertently cover more than intended.

See this entry in the whole of v2.1.267 →

Feedback