{"version":"2.1.271","anchor":"artifact-preview-chrome-discovery-gains-bun-chrome-path-over","canonical_anchor":"artifact-preview-chrome-discovery-gains-bun-chrome-path-over","heading":"Artifact preview Chrome discovery gains BUN_CHROME_PATH override and multiple candidates","tier":"use","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/artifact-preview-chrome-discovery-gains-bun-chrome-path-over","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Artifact preview Chrome discovery gains BUN_CHROME_PATH override and multiple candidates\n\nArtifact preview's Chrome discovery now checks BUN_CHROME_PATH first and tries multiple candidate binaries\n\n**What**\n\nWhen Claude Code looks for a Chrome browser to render artifact previews, it now checks the `BUN_CHROME_PATH` environment variable first. If that isn't set, it builds a list of candidates combining Playwright's bundled Chrome with another discovery source, rather than resolving to a single Chrome path immediately. The preview tool's safety check, which refuses to launch a Chrome binary sitting somewhere the current session could have planted or altered, now runs over this whole list of candidates and reports every candidate it refused in its error message.\n\n**Why**\n\nThis gives preview more places to find a usable Chrome binary, and makes it clearer, when none pass the safety check, exactly which candidates were tried and rejected.\n\n- Area: Artifacts\n- Names: `BUN_CHROME_PATH`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}