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.248 Home All releases olderv2.1.247 v2.1.250newer
Claude Code v2.1.248

Local artifact replicas are wired up but can never serve a read

Not switched on
Useful1 Signal4
Artifacts

Artifact reads still all go to the server; the local-copy path exists but nothing fills it.

Artifact sessions carry renderer, transport and engine slots for serving reads locally, but nothing populates them and no flag exists.

What

Artifact sessions gained a block of state for serving artifact reads from a local copy instead of fetching them, including a renderer, a transport and an engine slot. Nothing in this build ever fills those slots, so the optional call always short-circuits and every artifact read still goes to the server. No flag controls this; the code that would populate it is not shipped.

Details
  • The state block holds replicas, unavailable, opening, transport, engine, renderLevel and headMoved.
  • The read path calls the renderer with the artifact slug and head sequence; on a hit it would log a line about serving from the local replica and return HTML locally.
  • The only writes present are the initialiser and three calls that clear the block.
Evidence

read served from the local replica at seq

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