Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.292 ·

Artifact preview gains an emulator engine for cloud sessions

Artifact preview can pick a cloud emulator engine instead of local Chrome, though in the code examined a built-in switch keeps it off

Group of 2 You'll notice Nothing to try yet In Development
JSON All of v2.1.292
You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
5Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
In DevelopmentKind: in v2.1.292,
What probably matters to youSection of the release

Unclear It is not clear whether anything in this release ever turns the internal switch on, so the emulator may or may not be reachable.

What

Artifact preview lets Claude look at a page it built. It can now choose between two engines: local_chrome, the existing local headless browser, and a new emulator that downloads the real artifact viewer on first use and runs it without a window inside a cloud session. Two new per-session state fields, artifactPreviewEmulator and artifactPreviewEngine, hold the choice.

  • The emulator is picked only when CLAUDE_CODE_ARTIFACT_PREVIEW is not false, CLAUDE_CODE_REMOTE is true, a built-in switch in the code is on, and the emulator check passes.
  • The emulator check: CLAUDE_CODE_ARTIFACT_PREVIEW_EMULATOR set to false turns it off; missing or unreadable emulator files under /mnt/skills (examples/artifact-emulator), which must also pass ownership and permission checks, turn it off; CLAUDE_CODE_ARTIFACT_PREVIEW_EMULATOR set to true turns it on; otherwise a server-side setting decides, defaulting to off.
  • When the emulator is in use, the tool tells the model "Look at a local page in the real artifact viewer inside this cloud session. Nothing is published.", drops the width and theme options, and describes file_path as "the page's .html file to look at in the artifact viewer."

In the code one finding examined, the built-in switch starts off and nothing seen turns it on, so the engine falls back to local_chrome; the whole program was not searched. A related check in the local preview path also stays false for the same reason.

Why

This prepares a way to preview artifacts in the real viewer during cloud sessions. For now, expect previews to keep using the local browser engine.

Read from
Feature flag
tengu_cobalt_plinth_aspen 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.292: 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.292. It isn't a statement about your account. What a flag value here can and cannot tell you

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear whether anything in this release ever turns the internal switch on, so the emulator may or may not be reachable.

See this entry in the whole of v2.1.292 →

Feedback