{"version":"2.1.267","anchor":"artifact-write-db-permission-prompts-now-describe-file-prove","canonical_anchor":"artifact-write-db-permission-prompts-now-describe-file-prove","heading":"Artifact write_db permission prompts now describe file provenance and version-pinned edits to others' artifacts","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/artifact-write-db-permission-prompts-now-describe-file-prove","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Artifact write_db permission prompts now describe file provenance and version-pinned edits to others' artifacts\n\nPermission prompts for writing to artifacts now explain whose file it is and flag version-pinned edits\n\n**What**\n\nWhen 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.\n\nIt 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.\n\n**Why**\n\nThis 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.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}