{"version":"2.1.319","anchor":"artifact-db-read-db-save-can-now-overwrite-existing-files-w","canonical_anchor":"artifact-db-read-db-save-can-now-overwrite-existing-files-w","heading":"Saving artifact database reads can now replace some existing files","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/artifact-db-read-db-save-can-now-overwrite-existing-files-w","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Saving artifact database reads can now replace some existing files\n\nWhen `read_db` saves documents as JSON files, it can now replace an existing file in some cases and skips others with `existing_file`\n\n**Unclear.** Which conditions allow an existing file to be replaced rather than skipped is not known.\n\n**What**\n\nThe `read_db` action can save documents from an artifact's database as JSON files on your machine. Before, it never wrote over a file that was already there.\n\nIt can now replace existing files in some cases. Documents that would overwrite a file in other cases are skipped with the reason `existing_file`, and the number skipped is counted in Claude Code's usage reporting. It also now keeps a marker file alongside the write, and a problem with that marker is reported as its own outcome.\n\n**Why**\n\nA save from `read_db` can now change files already on disk, where before it would only create new ones.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}