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

The first artifact database write names the local file it reads from

You'll notice
Useful3 Signal3
Artifacts

The first artifact database write shows which local file it reads and why approval is manual.

What

The approval prompt for an artifact database write now shows the local file the document comes from, and lists reasons the automatic permission classifier cannot approve it: a path whose spelling can name a different file, a path resolving outside the allowed read paths, and a hard-linked source.

Details
  • The prompt no longer promises session-wide coverage when the write is not one that can be covered for the session.
Evidence

the path\u2019s spelling can name a different file than it appears to \u2014 approval must come from the user, not the auto-permission classifier

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 →