{"version":"2.1.292","anchor":"artifact-preview-can-run-in-a-cloud-emulator","canonical_anchor":"artifact-preview-emulator-engine-is-built-but-cannot-be-se","heading":"Artifact preview gains an emulator engine for cloud sessions","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/artifact-preview-can-run-in-a-cloud-emulator","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Artifact preview gains an emulator engine for cloud sessions\n\nArtifact preview can pick a cloud emulator engine instead of local Chrome, though in the code examined a built-in switch keeps it off\n\n**What**\n\nArtifact 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.\n\n- 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.\n\n- 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.\n\n- 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.\"\n\nIn 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.\n\n**Why**\n\nThis prepares a way to preview artifacts in the real viewer during cloud sessions. For now, expect previews to keep using the local browser engine.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 5\/5\n- Scope: individual\n- Heads-up: no"}