Artifact database reads can dump fetched documents into a folder on disk instead of into the chat.
What's wrong with this entry?
Artifact database reads take an out_dir and write each returned document to disk as a JSON file instead of pulling it into the conversation. The result line reports how many documents were saved and how many were skipped.
- The destination is resolved first: directories that cannot be resolved, and network paths, are refused outright.
- Every planned file is run through the same safety rules that govern file edits before anything is written.
- The approval prompt is rewritten for this case, telling you the documents will be saved as JSON files at the named location.
read_db saves only to local directories \u2014 out_dir cannot be resolved, read_db saves only to local directories \u2014 out_dir names a network path or cannot be resolved
Strings lifted out of the shipped bundle, so the claim above can be checked against them.