tengu_artifact_hljs_highlight Not enough to sayNothing 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: off
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
What's wrong with this entry?
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.
- Feature-flagged via
tengu_artifact_hljs_highlight(default: true). - The hljs bundle is loaded from
/$bunfs/root/hljsBundle.generated.min.jsand 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"
"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.