Unclear Which conditions allow an existing file to be replaced rather than skipped is not known.
What
The 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.
It 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.
Why
A save from read_db can now change files already on disk, where before it would only create new ones.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Which conditions allow an existing file to be replaced rather than skipped is not known.