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
Record the AUDIT YOURSELF procedure (icons are MANDATORY) + fix the three regressions that audit found. John, twice: 'when i say audit your windows, i mean check your icons too'. SKILL.md and pup-bridge-test now carry a seven-section self-audit: sessions, ICONS/TASKBAR (per-window overlay + AUMID key count + an ON-GLASS taskbar screenshot, because the API reports a badge applied while it is invisible), OS ground truth, health, log (explicitly surfacing park-failed and reclaim-adopted lines), Chrome footprint split pup-vs-user, and cleanup state — with the rule to state what is WRONG first and name your own regressions. Fixes from running it: (1) recovered windows came back with NO badge — under minimalTouch the overlay applies only on open/navigate and the re-stamp sweeps are gated off, so every bridge restart left surviving windows bare; recovery now re-wears it. (2) RECLAIMED/adopted windows were never badged either; they are now. (3) park-failed was logged and then ignored, leaving a window wherever Chrome put it (possibly on the user's screen, the one thing park exists to prevent) — it now retries before falling back to the AD verb.
4 files changed
+26−6
adom-bridge-puppeteer-manifest.json+4−4@@ -1,10 +1,10 @@ { "manifest_version": 1, "name": "puppeteer",- "version": "1.9.201",- "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.201/adom-bridge-puppeteer-v1.9.201.zip",- "sha256": "517353f5df2a76857da789c86b9dcd9b5e2d7fd9d4a460664a331be906f62085",- "size": 434015,+ "version": "1.9.202",+ "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.202/adom-bridge-puppeteer-v1.9.202.zip",+ "sha256": "2b748afa8f4e1e9cb642b982828ddd1f9445fee7392aa1f16f31175a06313ba6",+ "size": 434684, "verbPrefixes": [ "browser_", "desktop_recorder_",
src/BRIDGE_VERSION+1−1@@ -1 +1 @@-1.9.201+1.9.202
src/bridge.json+1−1@@ -2,7 +2,7 @@ "manifest_version": 1, "name": "puppeteer", "displayName": "Puppeteer (Chrome for Testing + Native)",- "version": "1.9.201",+ "version": "1.9.202", "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. 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, browser_alert_window posts a native toast whose click focuses the window, browser_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-desktop", "author": "Adom Inc.",
src/server.js+20@@ -1675,6 +1675,11 @@ async function recoverSessions() { // park below yanked a window the user was actively using to the bottom (John, 2026-07-29). if (sf.foreground) { session._foreground = true; session._userActiveAt = Date.now(); } if (sf.owner) session.owner = sf.owner; // v1.9.197 BUG 4: restore ownership across restarts+ // v1.9.202 (John's icon audit): a recovered window came back with NO taskbar badge. Under+ // minimalTouch the overlay is applied only on OPEN and NAVIGATE, and the re-stamp sweeps that+ // used to cover recovery are gated off — so every bridge restart left surviving windows bare+ // (drew-nsf-pcl had favicon+adom:wiki.adom.inc, then lost it). Re-wear it after recovery.+ setTimeout(() => { applyAppOverlay(session, sessionId).catch(() => {}); }, 2500); sessions.set(sessionId, session); const be = browsers.get(profileName); if (be) be.refCount++;@@ -4341,6 +4346,10 @@ async function reclaimUnmanagedWindows() { try { await retagSessionTitle(group[0], newId, profileName); } catch (e) {} console.log(`[reclaim] UNMANAGED window on "${profileName}" (${group.length} tab(s)) adopted as "${newId}" — ${(u || '').slice(0, 60)}`); refreshWindowChrome(ns, newId).catch(() => {});+ // v1.9.202: an ADOPTED window also needs its badge — refreshWindowChrome is gated off under+ // minimalTouch, so without this a reclaimed window (John's "durable-win55fa", 4 PDF tabs)+ // stays permanently unbadged.+ setTimeout(() => { applyAppOverlay(ns, newId).catch(() => {}); }, 2500); // v1.9.70: a RECLAIMED window was never parked either. These are windows pup did not launch // (an openerless popup, or an orphan whose session died), so they arrive wherever the shell // put them — usually on top. Background them like any pup-launched window.@@ -5223,6 +5232,17 @@ async function reassertBottomAfterNav(sessionId) { if (hwnd && osBottomUnlessForeground(hwnd, true) === 'bottomed') bottomed = true; } catch (e) {} if (bottomed) { console.log(`[park] "${sessionId}" (post-nav re-assert): bottomed`); return; }+ // v1.9.202 (John's log audit found `park-failed` on two windows and pup just moved on): a+ // park-failed window is sitting WHEREVER CHROME LEFT IT — i.e. possibly on the user's screen, which+ // is the one outcome park exists to prevent. Retry once after a beat before falling back to AD.+ try {+ await new Promise(r => setTimeout(r, 1200));+ const hwnd2 = await cachedSessionHwnd(sessionId);+ if (hwnd2 && osBottomUnlessForeground(hwnd2, true) === 'bottomed') {+ console.log(`[park] "${sessionId}" (post-nav re-assert, retry): bottomed`);+ return;+ }+ } catch (e) {} try { await chrome.adCommand('desktop_set_window_state', { titleContains: `(session: ${sessionId}`, state: 'bottom', force: false }, { timeoutMs: 5000 , caller: sessionCaller(sessions.get(sessionId))}); } catch (e) {}