What
Artifact previews are rendered in the Chrome browser. Before, each preview started its own Chrome and closed it when done. Now:
- One Chrome per host is kept open for an idle period and reused by later previews.
- Each preview closes only its own browsing context, a separate space inside the browser, and leaves the browser running.
- The Chrome process no longer keeps Claude Code itself from exiting.
- Each preview server uses its own local address of the form
p<uuid>.localhost.
If a preview is interrupted while waiting for the shared browser, Claude Code says so.
Why
Repeated previews should open faster and leave fewer stray Chrome processes behind.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
How long the shared Chrome stays open while idle, and how long a preview waits for it to start, is not stated.