{"version":"2.1.292","anchor":"artifact-preview-can-use-an-in-session-emulator-instead-of","canonical_anchor":"artifact-preview-can-use-an-in-session-emulator-instead-of","heading":"Artifact previews can use a viewer inside the session instead of local Chrome","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/artifact-preview-can-use-an-in-session-emulator-instead-of","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Artifact previews can use a viewer inside the session instead of local Chrome\n\nPreviewing an artifact can now open a private copy in an artifact viewer inside the session and return pictures, instead of using local Chrome\n\n**Unclear.** What decides whether the emulator or local Chrome is used is not known.\n\n**What**\n\nWhen Claude previews an artifact, Claude Code now chooses between two ways of doing it:\n\n- `local_chrome`, which renders it in a headless browser (a browser with no window) on your machine and returns screenshots, as before.\n\n- An emulator, which opens a private copy of the artifact in an artifact viewer inside the session and returns pictures.\n\nThe emulator comes with its own permission prompt, saying Claude wants to look at the artifact in the artifact viewer inside this session. When it fails, Claude is told not to try checking the artifact some other way.\n\n**Why**\n\nIn some setups this removes the need for Chrome on your machine to preview an artifact. If you see the new permission prompt, the preview is being done inside the session instead of in a local browser.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}