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
Raising a window that is ALREADY the user's foreground window is now a silent no-op: clicking a control inside the window (the toolbar Annotate button) triggered the foreground raise machinery plus the caption explaining a raise that did nothing, drawing noise over the user's work. osRaiseSessionWindow now checks the OS foreground first; an already-front window gets only a CDP tab bringToFront, no OS raise and no caption. Genuine background raises keep the caption etiquette unchanged.
4 files changed
+25−6
adom-bridge-puppeteer-manifest.json+4−4@@ -1,10 +1,10 @@ { "manifest_version": 1, "name": "puppeteer",- "version": "2.0.135",- "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.135/adom-bridge-puppeteer-v2.0.135.zip",- "sha256": "58fdedc245f3a0cdd09f90d1766509f14d4d6efe7ba6539f9b24ec8141896073",- "size": 889015,+ "version": "2.0.136",+ "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.136/adom-bridge-puppeteer-v2.0.136.zip",+ "sha256": "cca01fa85cb93e575562496ffd72fe00f7a20140990a4c01aa0b37ac3e9b6b70",+ "size": 889390, "verbPrefixes": [ "browser_", "desktop_recorder_",
src/BRIDGE_VERSION+1−1@@ -1 +1 @@-2.0.135+2.0.136
src/bridge.json+1−1@@ -2,7 +2,7 @@ "manifest_version": 1, "name": "puppeteer", "displayName": "Puppeteer (Chrome for Testing + Native)",- "version": "2.0.135",+ "version": "2.0.136", "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+19@@ -6330,6 +6330,25 @@ async function wikiCaption(text, expiresInMs) { // clear WS_EX_NOACTIVATE + SetForegroundWindow (via the detached/browser PID, with a WMI child // fallback for launcher→browser PID relaunches). Best-effort throughout; never throws. async function osRaiseSessionWindow(session, sessionId, reason) {+ // v2.0.136 (John: "why are you showing this caption when i click annotate in the chrome bar?"):+ // if this window is ALREADY the user's foreground window, there is nothing to bring to the+ // front — the user is literally looking at it (they just clicked a control inside it, e.g. the+ // toolbar Annotate button). The raise was a no-op, but the choke-point caption explaining the+ // "raise" fired anyway — pure noise over their work. Early-exit: an already-foreground window+ // gets a CDP tab bringToFront only (so the right tab shows), no OS raise, NO caption. Raises+ // of genuinely background/minimized windows behave exactly as before, caption included.+ if (process.platform === 'win32') {+ try {+ const _fgNow = await osGetForegroundWindow();+ const _myH = session._hwnd ? Number(session._hwnd) : (await sessionHwnd(sessionId));+ if (_fgNow && _myH && Number(_fgNow) === Number(_myH)) {+ session._foreground = true;+ try { await session.page.bringToFront(); } catch (e) {}+ console.log(`[foreground] "${sessionId}" is already the user's foreground window — raise + caption skipped (no-op)`);+ return;+ }+ } catch (e) {}+ } // v1.9.255 (John: "if a user asks to fg, you show a caption for 2 seconds explaining the reason. // do you do that? cuz i asked you 100 times"): the pup_raise verb captioned, but the five // OTHER raise paths routed here and captioned NOTHING. Enforce at the choke point: every raise