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

Claude Code v2.1.251 ·

Nested runtime-marker wrapper detection blocks artifact/page publishing

Publishing stops if your page got wrapped repeatedly in runtime scaffolding, asking for the innermost document.

Group of 2 You'll notice New Features
JSON All of v2.1.251
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
New FeaturesKind: in v2.1.251,
New FeaturesSection of the release

Artifact and page publishing now detects content recursively wrapped in repeated runtime marker blocks, such as <!-- frame-runtime -->, data-frame-runtime, <!-- chart-runtime -->, mermaid/hljs marker blocks, <base href="/_f/..."> skeletons, or repeated <!doctype html> skeletons. The code explicitly notes this is a pattern that "nothing a genuine page or a fetched artifact contains."

New unwrap logic (MDt/oi/So plus the zRe error class) caps how many nested skeleton/wrapper layers it will unwrap before refusing to publish. When the cap is hit, publishing is refused with an explicit instruction telling the author to delete the fake/nested wrapper markup and republish just the innermost document.

See this entry in the whole of v2.1.251 →

Feedback