{"version":"2.1.287","anchor":"artifact-preview-shares-a-pooled-chrome-with-per-host-localh","canonical_anchor":"artifact-preview-shares-a-pooled-chrome-with-per-host-localh","heading":"Artifact previews reuse one shared Chrome instead of starting a new one each time","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/artifact-preview-shares-a-pooled-chrome-with-per-host-localh","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Artifact previews reuse one shared Chrome instead of starting a new one each time\n\nArtifact previews now share a Chrome browser kept open for a while and reused, instead of launching and closing Chrome for every preview\n\n**Unclear.** How long the shared Chrome stays open while idle, and how long a preview waits for it to start, is not stated.\n\n**What**\n\nArtifact previews are rendered in the Chrome browser. Before, each preview started its own Chrome and closed it when done. Now:\n\n- One Chrome per host is kept open for an idle period and reused by later previews.\n\n- Each preview closes only its own browsing context, a separate space inside the browser, and leaves the browser running.\n\n- The Chrome process no longer keeps Claude Code itself from exiting.\n\n- Each preview server uses its own local address of the form `p<uuid>.localhost`.\n\nIf a preview is interrupted while waiting for the shared browser, Claude Code says so.\n\n**Why**\n\nRepeated previews should open faster and leave fewer stray Chrome processes behind.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}