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.239 Home All releases olderv2.1.238 v2.1.240newer
Claude Code v2.1.239

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

Not switched on
Useful2 Signal4
Artifacts

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

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 →