app
Pup - the AI's own browser
Public Made by Adomby adom
pup gives your AI a real browser on your desktop that it drives completely, in the background, signed in as you: windows that never jump in front of your work, one shared profile that learns your logins, and every window labeled on the taskbar with its AI thread's name.
← Commit history
v2.0.272: Fix adom/pup-bridge#69: pup_switch_tab reported ok while never switching the tab on any background window. page.bringToFront() is the only thing that actually changes Chrome's visible tab and it was gated on session._foreground; pup windows are background by default, so the normal case updated pup's own activeTabId bookkeeping, never told Chrome, and still returned success:true, while pup_list_tabs (which reads Chrome's real state) kept reporting the old tab. Reproduced on AdomLapper against a 3-tab window: asking for tab-1, tab-2 or tab-3 all left Chrome on tab-2. The v1.8.26 rationale was 'only raise the OS window for a session the user is watching', which conflated activating a TAB inside a window with raising that window. The activation now always runs, and because Target.activate can pull a window forward, the user's focus is handed straight back with the same one-shot handback used at window birth in 2.0.259 (never a timer, never a loop, the window itself is never moved). The verb also VERIFIES the switch by reading visibilityState back from Chrome and returns activated plus an honest hint when it did not take, because a verb that says ok while nothing happened is the exact class this issue is about.
4 files changed
+38−11
adom-bridge-puppeteer-manifest.json+5−5@@ -1,10 +1,10 @@ { "manifest_version": 1, "name": "puppeteer",- "version": "2.0.271",- "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.271/adom-bridge-puppeteer-v2.0.271.zip",- "sha256": "1e41d310fd196ef2ef0dbd5b153cc9b3a740bb3ad80ba4b8ec47152e378d451e",- "size": 961874,+ "version": "2.0.272",+ "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.272/adom-bridge-puppeteer-v2.0.272.zip",+ "sha256": "7007abab82fe336139871f8473ee82da2531ce800e5ae01114f41eda0db7dbb6",+ "size": 962731, "verbPrefixes": [ "browser_", "desktop_recorder_",@@ -12,5 +12,5 @@ ], "healthEndpoint": "/status", "statusVerb": "browser_readiness",- "released_at": "2026-08-21T18:53:46.411785Z"+ "released_at": "2026-08-21T19:28:42.525899Z" }
src/BRIDGE_VERSION+1−1@@ -1 +1 @@-2.0.271+2.0.272
src/bridge.json+1−1@@ -2,7 +2,7 @@ "manifest_version": 1, "name": "puppeteer", "displayName": "Puppeteer (Chrome for Testing + Native)",- "version": "2.0.271",+ "version": "2.0.272", "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. pup_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. pup_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. macOS (v1.9.74+): full parity with mac-native mechanics \u2014 background-by-default is the app-level hide (windows stay drivable/screenshottable while hidden), raise/lower map to unhide+activate/hide, pup_alert_window posts a native toast whose click focuses the window, pup_use {browser:'chrome',install:true} installs Chrome from the official dmg, and taskbar identity/badging remains Windows-only.", "homepage": "https://wiki.adom.inc/adom/adom-bridge", "author": "Adom Inc.",
src/server.js+31−4@@ -15597,9 +15597,30 @@ const server = http.createServer(async (req, res) => { return; } session.activeTabId = tab.tabId;- // v1.8.26: only raise the OS window for a session the user is watching. For a- // background window, just track the active tab (pup targets tabs by id).- if (session._foreground) { try { await tab.page.bringToFront(); } catch {} }+ // v2.0.272 (#69, reported against 2.0.269): THIS VERB USED TO LIE ON EVERY BACKGROUND+ // WINDOW. `page.bringToFront()` is the only thing that actually switches Chrome's visible+ // tab, and it was gated on `session._foreground`. pup windows are background BY DEFAULT,+ // so the normal case updated pup's own `activeTabId` bookkeeping, never told Chrome, and+ // still returned success:true — while pup_list_tabs (which reads Chrome's real state)+ // kept reporting the old tab. Two verbs disagreeing, with the honest one looking broken.+ // The v1.8.26 rationale was "only RAISE THE OS WINDOW for a session the user is watching",+ // which conflated two different things: activating a TAB inside a window is not the same+ // as raising that window. The legitimate worry underneath is real though — Target.activate+ // can pull the window forward — so do the activation ALWAYS and hand the user's focus+ // straight back, exactly the one-shot handback used at window birth (v2.0.259). Never a+ // timer, never a loop; the window itself is never moved.+ let _fgBefore = null;+ try { if (!session._foreground && process.platform === 'win32') _fgBefore = await osGetForegroundWindow(); } catch (e) {}+ try { await tab.page.bringToFront(); } catch (e) {}+ if (_fgBefore) {+ try {+ const _after = await osGetForegroundWindow();+ if (_after && String(_after) !== String(_fgBefore)) {+ console.log(`[switch-tab] "${sessionId}" activating ${tab.tabId} pulled the window forward — handing focus back to ${_fgBefore}`);+ await chrome.abCommand('desktop_bring_to_front', { hwnd: Number(_fgBefore) }, { timeoutMs: 4000 });+ }+ } catch (e) {}+ } // v1.8.57: switch_tab is a long-lived app's hot path (adom-shotlog switches its // shared window's tabs for hours) — self-heal a stranded window + re-badge here // (debounced) so the window stays clickable/badged across bridge restarts.@@ -15612,8 +15633,14 @@ const server = http.createServer(async (req, res) => { brandPupWindow(sessionId).then(ok => { if (ok) session._badgedAt = Date.now(); }).catch(() => {}); } }+ // v2.0.272: VERIFY, do not assert. #69's whole complaint is a verb that reports ok while+ // nothing happened, so read the activation back from Chrome and say so when it did not take.+ let _isActive = null;+ try { _isActive = await withTimeout(tab.page.evaluate('document.visibilityState'), 1500, 'switch-verify') === 'visible'; } catch (e) {} const info = await describeTab(tab, session.activeTabId);- sendJSON(res, { success: true, output: JSON.stringify({ ok: true, sessionId, ...info }) });+ sendJSON(res, { success: true, output: JSON.stringify({ ok: true, sessionId, ...info,+ activated: _isActive,+ ...(_isActive === false ? { _hint: `pup switched its OWN pointer to ${tab.tabId}, but Chrome still does not report that tab as visible. Confirm with pup_list_tabs (it reads Chrome, not pup's bookkeeping) before trusting the switch, and please report it on adom/pup-bridge — a verb that says ok while nothing moved is the exact class issue #69 closed.` } : {}) }) }); return; } case 'pup_close_tab': {