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.224 Home All releases olderv2.1.223 v2.1.225newer

Artifact tool gains document-store read and write

Not switched on
Useful3 Signal4
Artifacts

Artifacts get document read and write operations with separate remembered consent for each.

The document-store operations are part of the artifact database work that stays gated off.

What

New read and write operations address documents by page address, collection path and document id, with errors for a bad address, an over-long composed path and a missing document id. Consent is remembered separately for reads and writes, and again separately for approvals given by a person in plan mode.

Details
  • The stored consent covers write approval, human write approval, and per-address lists for read consent and human read consent.
  • Whether these operations are offered unconditionally or behind a flag is decided by the tool's schema, which is not resolved in this build.
Evidence

doc_id is required for a get

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.224 →