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.212 ·

Artifact Syntax Highlighting (tengu_artifact_hljs_highlight)

Entry
JSON All of v2.1.212
EntryKind: in v2.1.212,
New FeaturesSection of the release

Published artifacts that contain fenced code blocks now include an inline highlight.js (hljs) runtime for client-side syntax highlighting. The runtime is appended only when the artifact contains recognizable language classes.

Details
  • Feature-flagged via tengu_artifact_hljs_highlight (default: true).
  • The hljs bundle is loaded from /$bunfs/root/hljsBundle.generated.min.js and embedded inline so artifacts remain standalone.
  • A per-artifact token budget limits how much code gets highlighted to keep page load fast.
  • The runtime is validated before injection; unsafe bundles are rejected.
  • The artifact footer note now reads: "— includes the inline syntax-highlight runtime (~1MB), appended because the page contains fenced code"
Evidence

"bundle contains an hljs runtime sentinel" (search for "tengu_artifact_hljs_highlight")

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Feature flag
tengu_artifact_hljs_highlight 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.212: on

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

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

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_artifact_hljs_highlight

See this entry in the whole of v2.1.212 →

Feedback