Pup - the AI's own browser

@@ -1,5 +1,14 @@ # Changelog — Adom Desktop Puppeteer Bridge +## 1.8.52 — 2026-07-14 — Close the launch gap: a click during the first ~2s now shows the window++With 1.8.51, a taskbar click during the launch gap (window still at its off-screen coords, park PS+still starting) activated an invisible off-screen window — the user saw nothing for ~2s. Now the park+checks the foreground first, and the check is UNAMBIGUOUS because `--no-startup-window` means Chrome+cannot raise itself: pup-window-foreground can only be the user. If the user clicked during the gap,+the park places the window on-screen at the TOP full-size and leaves them focused on it+(`user-foreground`); otherwise it parks to z-bottom as usual. Either way it exits — still no loops.+ ## 1.8.51 — 2026-07-14 — `--no-startup-window`: eliminate the focus steal at the SOURCE (no more war)  John proved a taskbar click within the first couple seconds still got yanked (the 1.8.50 stability

@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "version": "1.8.51",-  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.8.51/adom-bridge-puppeteer-v1.8.51.zip",-  "sha256": "0ac560a2ce4f660ab55ee26b9ada08b8a731ef305474f94ec968262cbf318dd5",-  "size": 166663,+  "version": "1.8.52",+  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.8.52/adom-bridge-puppeteer-v1.8.52.zip",+  "sha256": "cd1726eee1858edccc62c7f154d85efa7cb5d63436cabcc4a5bba83181c570b0",+  "size": 166799,   "verbPrefixes": [     "browser_",     "desktop_recorder_",

@@ -1 +1 @@-1.8.51\ No newline at end of file+1.8.52\ No newline at end of file

@@ -2,7 +2,7 @@   "manifest_version": 1,   "name": "puppeteer",   "displayName": "Puppeteer (Chrome for Testing + Native)",-  "version": "1.8.51",+  "version": "1.8.52",   "description": "Drives a browser ALREADY on the machine \u2014 installed Chrome, else Microsoft Edge (every Windows PC ships with Edge) \u2014 launched with a FRESH isolated profile, so the common case has NO ~150 MB Chrome-for-Testing download and it never touches the user's real tabs/logins. Binds its local server to LOOPBACK (127.0.0.1) only, so no Windows Firewall 'allow Node through the firewall' prompt ever pops. Chrome for Testing is fetched only as a LAST RESORT if the machine has no Chromium browser at all. SPAWN-VERIFIED fallback: pup tries each detected browser (Chrome \u2192 Edge \u2192 CfT) and actually launches it, falling through to the next if one won't start (and handling browsers like Edge that relaunch onto another PID), so a corrupt/partial install never hard-fails an open. The browser that launches is cached as the default (persisted across restarts) so it isn't re-probed each time. On spawn the bridge SELF-WARMS: detects browsers + disk, and only if the box has no Chrome/Edge and no cached CfT does it background-fetch CfT so the first open is instant. browser_use pins a specific browser (chrome | edge | cft | auto); {browser:'chrome',install:true} downloads & installs REAL Google Chrome (user-scoped, no admin) on an Edge-only box. browser_readiness (READ-ONLY) reports which browser will be used + the full candidate list + the default + free disk. Every failure returns a specific errorCode + _hint (chrome_install_no_disk, chrome_download_network, chrome_install_permission, chrome_stable_not_detected, \u2026). Launches with FULL browser permissions by default for full debug (strictPermissions:true opts out). Headful automation: open/close windows+tabs, navigate, screenshot, eval JS, record. pup is a GENERIC, non-profile browser only \u2014 every session is a fresh isolated Chrome/Edge process, never the user's real signed-in browser; profile defaults to sessionId. To drive the user's REAL Chrome/Edge (their profile, cookies, SSO), use the Adom browser EXTENSION's nbrowser_* verbs \u2014 a separate bridge, not pup's job.",   "homepage": "https://wiki.adom.inc/adom/adom-desktop",   "author": "Adom Inc.",

@@ -1794,11 +1794,18 @@ async function osBackgroundWatchdog(pid, cdpPort, restoreHwnd) {       '  Start-Sleep -Milliseconds 50',       '}',       'if ($pup -eq [IntPtr]::Zero) { Write-Output "no-window"; exit }',-      // 2. Park ONCE: hand back focus only if Chrome somehow took it (with --no-startup-window-      //    the OS denies it the foreground, so this is normally a no-op), then move on-screen-      //    at z-bottom. NO stability loop — there is no self-raise to fight anymore, and any-      //    watch loop inevitably fights a user's early taskbar click (John proved it: clicking-      //    within the first couple of seconds got yanked back). Park, verify, EXIT.+      // 2. Park ONCE — with a user-click escape hatch that is now UNAMBIGUOUS: because+      //    --no-startup-window means Chrome cannot raise itself, "pup window is foreground"+      //    can only mean THE USER clicked its taskbar button during the launch gap (while the+      //    window was still at its off-screen coords, where activating it shows nothing). In+      //    that case: place it on-screen at the TOP full-size, keep the user's focus on it,+      //    and report user-foreground. Otherwise: single SetWindowPos to on-screen z-bottom.+      //    Park, verify, EXIT — nothing runs after this either way.+      '$fg1 = [WinWd]::GetForegroundWindow()',+      'if ($fg1 -eq $pup) {',+      '  [WinWd]::SetWindowPos($pup, [IntPtr]0, 0, 0, $scrW, $scrH, 0x40) | Out-Null', // HWND_TOP, SWP_SHOWWINDOW+      '  Write-Output "user-foreground"; exit',+      '}',       'HandBack $pup',       '[WinWd]::SetWindowPos($pup, $BOTTOM, 0, 0, $scrW, $scrH, $SWP) | Out-Null',       // 3. Self-verify and exit. Nothing runs after this — the user owns the window now.