Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.236 Home All releases olderv2.1.235 v2.1.237newer
Claude Code v2.1.236

read_db can save fetched documents to a local folder

Use it now
Useful4 Signal3
Artifacts Notable not in their notes

Artifact database reads can dump fetched documents into a folder on disk instead of into the chat.

out_dir
What

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.

Details
  • 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.
Evidence

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.

See this entry in the whole of v2.1.236 →