Source Intelligence
Follow Discord

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.233 Home All releases ←olderv2.1.232 v2.1.234newer→
Claude Code v2.1.233

Live artifacts ask the runtime for their write surface up front

You'll notice
Useful2 Signal1
Artifacts

Live artifacts load their write access once at startup, so the first edit feels faster.

What

All three artifact templates now request the artifact namespace once at load through claude.use('artifact') and cache it, instead of looking it up lazily on each edit, so the first edit rarely waits.

Details
  • Falls back to the old lazy claude.artifact || claude.self lookup when claude.use is not a function.
  • A new pending state covers the window between asking and answering: edits are tracked as if the document were live, and the status is not prematurely set to Local only. When the request resolves the template either saves the pending edits or reports Local only.
  • Off in this build; the templates only persist on live documents where the runtime grants the artifact capability.
Evidence

Ask for the namespace at load so the first edit rarely waits on it.

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