{"version":"2.1.318","anchor":"artifact-database-documents-by-others-are-not-saved-to-files","canonical_anchor":"artifact-database-documents-by-others-are-not-saved-to-files","heading":"Artifact database rows other people may have written can't be saved to files","tier":"notice","area":"Artifacts","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/artifact-database-documents-by-others-are-not-saved-to-files","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Artifact database rows other people may have written can't be saved to files\n\nReading an artifact's database into files is now refused when the rows may have been written by other people; leaving out `out_dir` still works\n\n**What**\n\nWhen Claude reads an artifact's database with `read_db` and asks to save the result to files, Claude Code now refuses if the rows may have been written by other people. The refusal tells Claude to leave out `out_dir`, the option that sets the folder to save into, so the rows are read without being saved.\n\n**Why**\n\nContent other people wrote can no longer reach your disk this way without being marked as theirs.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}