Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.308 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.248 ·

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

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

Nothing to try yet In Development
JSON All of v2.1.248
Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
In DevelopmentKind: in v2.1.248,
What probably matters to youSection of the release

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 →

Feedback