Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.247 Home All releases ←olderv2.1.246 v2.1.248newer→
Claude Code v2.1.247

Preview refuses a Chrome binary the session could have written

Under the hood
Useful1 Signal3
Artifacts

Preview refuses any Chrome binary sitting somewhere the session could have written to.

bypassPermissions
What

Before 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.

Details
  • Also denied: network-share paths, hard-linked source files, and files whose symlink target the Read rules would only permit after asking.
  • Otherwise preview asks once, with a prompt stating the render is local and nothing is uploaded.
  • If no Chrome is found, the error points at BUN_CHROME_PATH.
Evidence

Chrome not found: install Chrome or Chromium, or point BUN_CHROME_PATH at one.

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.247 →