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
Kill overlay drift at the source: one centralized debounced overlay re-sync now fires for every mutating verb (navigate/reload/back/forward/switch_tab/click/type/eval) plus close_tab/close_window, clearing the favicon cache and repainting via the ungated applyAppOverlay (refreshWindowChrome was a no-op under minimalTouch), without touching the cached handle so no routine verb triggers the wiggle
4 files changed
+36−7
adom-bridge-puppeteer-manifest.json+4−4@@ -1,10 +1,10 @@ { "manifest_version": 1, "name": "puppeteer",- "version": "1.9.300",- "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.300/adom-bridge-puppeteer-v1.9.300.zip",- "sha256": "21149edbc6027da8684e66493fbc0878813012412ad35858b65f43682070aa73",- "size": 724572,+ "version": "1.9.301",+ "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.301/adom-bridge-puppeteer-v1.9.301.zip",+ "sha256": "1d208e689b3e2b6a3d3d5b03a961cdee7018cc7aae4fa599046681d563173952",+ "size": 725229, "verbPrefixes": [ "browser_", "desktop_recorder_",
src/BRIDGE_VERSION+1−1@@ -1 +1 @@-1.9.300+1.9.301
src/bridge.json+1−1@@ -2,7 +2,7 @@ "manifest_version": 1, "name": "puppeteer", "displayName": "Puppeteer (Chrome for Testing + Native)",- "version": "1.9.300",+ "version": "1.9.301", "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+30−1@@ -314,6 +314,7 @@ const _profileOpenChain = new Map(); // profileName -> tail promise let _tabClaimSeq = 0; // monotonic per-call marker for in-window tab adoption (see addTabToSession) let _regenBusy = false; // a dashboard "regenerate all overlays" sweep is in flight let _lastRegen = null; // { at, done, swept, painted, changed, results[] } from the last sweep+const _overlayRefreshTimers = new Map(); // per-session debounce for the centralized post-verb overlay re-sync // v1.9.110 (issue #22, AdityaAngajala) — ADMISSION-TIME OWNERSHIP CLAIM. // Two defects he measured: (a) `owner` is optional, so in practice sessions end up unowned and the guard // that protects a busy window is opt-out by omission; (b) ownership was established when the BROWSER was@@ -5543,6 +5544,30 @@ async function refreshWindowChrome(session, sessionId, tries = 5) { console.log(`[chrome] "${sessionId}" could not refresh taskbar presence (window never became findable)`); return false; }+// v1.9.301 (John: "all the verbs that change tabs/windows/favicons, you just don't correctly+// trigger your overlay icon calculations"). The fix for drift-over-time: ONE centralized, debounced+// re-sync fired for EVERY mutating verb on an existing session (wired in the dispatch hook), instead+// of trusting each handler to remember. It clears the cached favicon pick so the NEW page's favicon+// is re-fetched, then calls the UNGATED applyAppOverlay (refreshWindowChrome is a no-op under+// minimalTouch, which is exactly why badges went stale). It does NOT clear the cached hwnd, so a+// routine verb never triggers the expensive width-wiggle — the handle is validated inside+// applyAppOverlay. Debounced per session (~2s) so a burst of verbs collapses to one repaint.+function scheduleOverlayRefresh(sessionId) {+ try {+ if (!sessionId) return;+ const prev = _overlayRefreshTimers.get(sessionId);+ if (prev) clearTimeout(prev);+ const t = setTimeout(() => {+ _overlayRefreshTimers.delete(sessionId);+ const s = sessions.get(sessionId);+ if (!s || !(s.tabs || []).length) return;+ s._overlayFav = null; s._faviconRetried = false; s._noFavLogged = false;+ applyAppOverlay(s, sessionId).catch(() => {});+ }, 2000);+ if (t.unref) t.unref();+ _overlayRefreshTimers.set(sessionId, t);+ } catch (e) {}+} // Brand a pup window: full identity on capable AD, overlay badge fallback on older AD. async function brandPupWindow(sessionId) { if (minimalTouch()) return false; // v1.9.185: no taskbar identity/branding in minimal mode@@ -9605,9 +9630,13 @@ const server = http.createServer(async (req, res) => { if (!isReadOnlyEval) { const sid = args.sessionId || activeSessionId; const s = sid && sessions.get(sid);- if (s) { recordAgentUpdate(s, command, args, args.tabId || s.activeTabId); scheduleAutoFlash(s, { silent: !!args.silent }); }+ if (s) { recordAgentUpdate(s, command, args, args.tabId || s.activeTabId); scheduleAutoFlash(s, { silent: !!args.silent }); scheduleOverlayRefresh(sid); } } }+ // v1.9.301: close_tab is NOT in MUTATING_VERBS but it changes the active tab (hence the favicon),+ // so it must re-trigger the overlay calc too. Centralize it here so no tab/window/favicon verb is+ // missed — the drift John called out.+ if (command === 'browser_close_tab' || command === 'browser_close_window') { try { scheduleOverlayRefresh(args.sessionId || activeSessionId); } catch (e) {} } // v1.9.70 — AUDIT EVERY INCOMING VERB. John: "do you even log all the actions against you?" // Fair — the log recorded what the bridge DID (park/identity/overlay) but never WHAT WAS ASKED