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

Claude Code v2.1.239 ·

Artifact embeds: parser and renderer ship, schema field does not

Artifact responses can carry pinned embed items that parse and render, but the schema key never ships.

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

The embeds parser and renderer are ungated but the schema field sits behind a constant set to false.

What

Artifact responses can now carry embeds, a list of pinned items (uuid, path, module, files) plus warnings, which is parsed from server responses and rendered into a readable block that cuts off with "(embeds truncated)". The parser and renderer are ungated, but the artifact tool's result schema declares the embeds key only inside a spread guarded by a module-level constant set to false, and that constant is used nowhere else.

Details
  • Whether an undeclared key survives result validation is not settled in this build, so it is unclear whether any embed text reaches the model.
  • No artifact embeds code exists in 2.1.238.
Evidence

(embeds truncated)

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

Feedback