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
Overlay badges can no longer silently vanish, the bare taskbar tile John caught that my log-trusting audit missed: the taskbar progress cycle (and other shell-side events) can clear a button's overlay, but pup's paint memory survived it, so the enforcer saw a painted window and never repainted, bare on screen while green in the logs. Windows offers no way to query overlay state, so the fix treats it as write-only: every progress change voids the paint memory (the 4s enforcer sweep repaints), and a 60s per-window ground-truth re-assert repaints unconditionally so memory can never drift from the screen for more than a minute. Also dedupes the sibling-favicon log line that spammed on every re-resolve
4 files changed
+24−7
adom-bridge-puppeteer-manifest.json+4−4@@ -1,10 +1,10 @@ { "manifest_version": 1, "name": "puppeteer",- "version": "2.0.46",- "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.46/adom-bridge-puppeteer-v2.0.46.zip",- "sha256": "c3bd7acb5b196f97d1c6b3d39a7bf9a54f73012266950b299af141fe7aa0cc26",- "size": 649480,+ "version": "2.0.47",+ "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.47/adom-bridge-puppeteer-v2.0.47.zip",+ "sha256": "48a4b71c36598371e28661de400376d17992fdb4d3fbff562fd5d41c7b68e695",+ "size": 650037, "verbPrefixes": [ "browser_", "desktop_recorder_",
src/BRIDGE_VERSION+1−1@@ -1 +1 @@-2.0.46+2.0.47
src/bridge.json+1−1@@ -2,7 +2,7 @@ "manifest_version": 1, "name": "puppeteer", "displayName": "Puppeteer (Chrome for Testing + Native)",- "version": "2.0.46",+ "version": "2.0.47", "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+18−1@@ -4112,6 +4112,12 @@ async function setSessionProgress(sessionId, busy) { progress: busy ? { state: 'indeterminate' } : { state: 'none' }, }, { timeoutMs: 4000 }); } catch (e) {}+ // v2.0.47 (John's zoom: a BARE tile my audit swore was painted): the taskbar progress cycle can+ // clear the button's overlay, but pup's paint memory (_appOverlay/_lastPaintSig) survives it, so+ // the enforcer "sees" a painted window and never repaints — bare on screen, green in the logs.+ // Windows offers no way to QUERY overlay state, so after every progress change assume the overlay+ // may be gone: void the paint memory and let the 4s enforcer sweep repaint (dedup makes it cheap).+ try { const _s3 = sessions.get(sessionId); if (_s3) { _s3._lastPaintSig = null; _s3._appOverlay = false; _s3._overlayEnforceAt = 0; } } catch (e) {} } // v1.9.166 (John, repeatedly: 'use an AD toast to get a human's attention'). Whenever pup FOREGROUNDS // a window (a reveal / demo / 'show me'), fire an AD toast FIRST so the user's eyes are drawn to what@@ -4928,7 +4934,8 @@ async function applyAppOverlay(session, sessionId) { if (!t || !t.page || t === activeTab || t._crashed) continue; const sib = await resolveFaviconRich(t.page).catch(() => null); if (sib && sib.b64) {- console.log(`[overlay] "${sessionId}" using sibling tab ${t.tabId}'s favicon (active tab has none)`);+ const _sk = `${t.tabId}|${sib.href || ''}`;+ if (session._sibFavLogKey !== _sk) { session._sibFavLogKey = _sk; console.log(`[overlay] "${sessionId}" using sibling tab ${t.tabId}'s favicon (active tab has none)`); } src = { b64: sib.b64, mime: sib.mime, href: sib.href }; session._overlayFav = { ...sib, kind: 'sibling-tab-favicon' }; break;@@ -5202,6 +5209,7 @@ async function applyAppOverlay(session, sessionId) { }, { timeoutMs: 5000 }); session._lastPaintSig = _paintSig; session._appOverlay = true;+ session._overlayReassertAt = Date.now(); // v2.0.47: fresh paint restarts the re-assert clock // v1.9.150 (John: 'prove what overlay icon you're showing and why'): record the WHAT and WHY // so list_windows can report it and test tables can prove it. session._overlayWhy = {@@ -14534,6 +14542,15 @@ const _onPupBound = async () => { s2._stampTriedAt = Date.now(); stampPupIdentity(sid2, { once: true }).catch(() => {}); } if (pupSettings().overlayBadges !== 'on') continue;+ // v2.0.47: GROUND-TRUTH RE-ASSERT. Overlay state is write-only (Windows can't be asked+ // whether the badge is still there), and shell-side events beyond the progress bar can+ // silently clear it. Every 60s per window, void the paint memory so the block below+ // repaints unconditionally — one cheap ab call per window per minute buys "the badge you+ // see is the badge we believe", instead of memory drifting from the screen forever.+ if (s2._appOverlay && Date.now() - (s2._overlayReassertAt || 0) > 60000) {+ s2._overlayReassertAt = Date.now();+ s2._lastPaintSig = null; s2._appOverlay = false;+ } const bare = !s2._appOverlay; // A window whose page genuinely has NO favicon anywhere sits on the generic glyph forever, and // the enforcer would re-fetch + re-compose it every 10s for the life of the window (John saw the