{"version":"2.1.247","anchor":"preview-refuses-a-chrome-binary-the-session-could-have-writt","canonical_anchor":"preview-refuses-a-chrome-binary-the-session-could-have-writt","heading":"Preview refuses a Chrome binary the session could have written","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/preview-refuses-a-chrome-binary-the-session-could-have-writt","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Preview refuses a Chrome binary the session could have written\n\nPreview refuses any Chrome binary sitting somewhere the session could have written to.\n\n**What**\n\nBefore rendering, preview resolves the Chrome executable, follows links, and denies with `preview_browser_in_workspace` if it sits under a working directory, a temp directory or a sandbox write root, or is hard-linked and writable. Sessions in `bypassPermissions` mode skip that check.\n\n**Details**\n\n- Also denied: network-share paths, hard-linked source files, and files whose symlink target the Read rules would only permit after asking.\n- Otherwise preview asks once, with a prompt stating the render is local and nothing is uploaded.\n- If no Chrome is found, the error points at `BUN_CHROME_PATH`.\n\n**Evidence**\n\n`Chrome not found: install Chrome or Chromium, or point BUN_CHROME_PATH at one.`\n\n- Area: Artifacts\n- Names: `bypassPermissions`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}