pup: browser_open_window forces Chrome-for-Testing even when system Chrome is installed and pinned (forced:true)

by adom

Adom Bridge unleashes your AI onto your full PC: full power, full safety. The AI breaks out of the container it runs in and onto your real machine, managing and running your entire laptop as you: launch apps, move files, drive any window, control KiCad, Fusion 360 or your real signed-in browser. Works with any AI, cloud or local (Claude Desktop, Claude Code, Codex), no Hydrogen required. Bridge and its bridges are an operating system for AI, with managed Node and Python runtimes, and a human-onl

Overview Files Skills Discover Packages Releases Dependencies Issues40 Breadcrumbs Pull Requests Activity

Open bug report

AdityaAngajala · 18d ago

Summary

On a Windows box with Google Chrome already installed, browser_open_window refuses to launch and instead insists on downloading Chrome for Testing (~150 MB) — even after browser_use {browser:"chrome"} pins system Chrome. browser_readiness reports the pin took effect (defaultBrowser.forced:true, source:"system"), but browser_open_window still gates on chromeForTestingInstalled and ignores it.

Environment

adom-desktop 1.9.168 (8d79bc3-dirty)
Windows; Chrome 146.0.7680.76 at C:\Program Files\Google\Chrome\Application\chrome.exe (Edge also present)
node v26.5.0; disk free ~363 GB

Repro

adom-desktop browser_use '{"browser":"chrome"}' → pins chrome. Readiness now shows defaultBrowser: {kind:"chrome", source:"system", forced:true, pendingInstall:false}.
adom-desktop browser_open_window '{"profile":"p","sessionId":"s","url":"https://example.com"}'
Result:

{ "ok": false,
  "errorCode": "chrome_for_testing_installing",
  "error": "Chrome for Testing (pup's dedicated sandboxed browser) is not cached yet — downloading it now (~150 MB, one time)." }

browser_readiness at the same moment (note system Chrome present AND forced):

{ "browserKind": "chrome",
  "browserSource": "system",
  "browserExecutablePath": "C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe",
  "defaultBrowser": { "kind": "chrome", "source": "system", "forced": true, "pendingInstall": false },
  "chromeForTestingInstalled": false }

Expected

With a system browser pinned/forced (forced:true), browser_open_window should launch it immediately and not require Chrome for Testing. The readiness hint itself advertises "have the user install Chrome or Edge … and pup uses it instantly" — but open_window still blocks on chromeForTestingInstalled regardless of the pin.

Impact

pup can't open a window at all until CfT provisions — and on this box CfT never finishes (see the companion issue about the CfT install stalling at 100%). A fresh profile already isolates identity, so using the forced system Chrome would be safe here.

Workarounds attempted (none worked)

browser_use {browser:"chrome"} — reflected in readiness, ignored by browser_open_window.
restart_bridge puppeteer — does not change the gate.

Adom Bridge