{"version":"2.1.236","anchor":"read-db-can-save-fetched-documents-to-a-local-folder","canonical_anchor":"read-db-can-save-fetched-documents-to-a-local-folder","heading":"read_db can save fetched documents to a local folder","tier":"use","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/read-db-can-save-fetched-documents-to-a-local-folder","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### `read_db` can save fetched documents to a local folder\n\nArtifact database reads can dump fetched documents into a folder on disk instead of into the chat.\n\n**What**\n\nArtifact 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.\n\n**Details**\n\n- The destination is resolved first: directories that cannot be resolved, and network paths, are refused outright.\n- Every planned file is run through the same safety rules that govern file edits before anything is written.\n- The approval prompt is rewritten for this case, telling you the documents will be saved as JSON files at the named location.\n\n**Evidence**\n\n`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`\n\n- Area: Artifacts\n- Names: `out_dir`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}