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.236 Home All releases olderv2.1.235 v2.1.237newer
Claude Code v2.1.236

Published Artifacts get stable per-block anchor ids

You'll notice
Useful3 Signal3
Artifacts

Published Artifacts get per-block anchor ids so links can point at a specific block.

Feature flag
tengu_cobalt_plinth_quince Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.236: off

Read once, for one account on one subscription tier, against v2.1.236. It isn't a statement about your account. What a flag value here can and cannot tell you

What

When publishing an Artifact, Claude Code now parses the document's HTML and gives each block-level element a short b-<hash> id derived from its tag and text, so links can point at a specific block. It runs only on documents carrying the // DOC:anchors:begin marker, and is gated on the flag tengu_cobalt_plinth_quince, whose built-in fallback is true, so it is on unless remote config disables it.

Details
  • Ids are written into the source before publish, rewriting existing id="..." attributes or inserting new ones.
  • The pass bails out and records telemetry when it cannot locate where the anchors script loads, when an id cannot be placed, when parsing throws, or when the text to hash exceeds 33554432 bytes.
Evidence

[artifact] doc block ids skipped: too much text to hash

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