pup: Chrome-for-Testing provisioning stalls at 100%/installing forever — ready never becomes true - Adom Bridge

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

pup: Chrome-for-Testing provisioning stalls at 100%/installing forever — ready never becomes true

AdityaAngajala · 18d ago

Summary

On first use, pup downloads Chrome for Testing to 100%, then wedges in the installing (extract) phase indefinitely. browser_readiness.ready never flips to true and chromeForTestingInstalled stays false. Observed stuck for >10 minutes with no error surfaced (lastError: null).

Environment

adom-desktop 1.9.168 (8d79bc3-dirty)
Windows; node v26.5.0; disk free ~363 GB (lowDisk:false); cache dir C:\Users\<user>\.cache\puppeteer
System Chrome 146 present (but not used — see companion issue on the pinned-Chrome gate)

Repro / observed

browser_open_window (first use) kicks off the CfT download.
browser_readiness reaches and then stalls at:

{ "ready": false,
  "installing": true,
  "installPhase": "installing",
  "installProgressPct": 100,
  "bytesDownloaded": 191442437,
  "bytesTotal": 191442437,
  "chromeForTestingInstalled": false,
  "lastError": null,
  "lastErrorCode": null }

It stays there indefinitely (>10 min observed). ready never becomes true; chromeForTestingInstalled never becomes true.
restart_bridge puppeteer resets progress to installProgressPct:0, bytesDownloaded:0 and re-downloads; the fresh attempt again reaches 100% and stalls at the same installing phase. Reproduced across multiple restarts.

Expected

After the download hits 100%, the extract/install step should complete (→ chromeForTestingInstalled:true / ready:true) within a reasonable time — or surface an actionable error into lastError / lastErrorCode if the extract fails, instead of an indefinite silent "installing".

Impact

pup cannot open any window on this box. Combined with the companion issue (pinned system Chrome is ignored by browser_open_window), there is no working path to a browser here — screenshots/driving are fully blocked.

Hypotheses / suggestions

Download completes (bytes match) but the unzip/extract of the CfT binary wedges — plausibly AV/Defender scanning or quarantining the extracted chrome.exe, or a stuck extraction. Nothing lands in lastError, so it presents as an infinite "installing".
Suggested fixes: add an extract-phase timeout that writes lastError/lastErrorCode; and/or, when CfT extraction fails or times out, fall back to the forced/available system Chrome so pup is still usable.

Adom Bridge