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
Debounce jump-list settle churn on open: coalesce the settle-driven refreshes (bare appId then category, public then authed view) into one commit so a single open updates the right-click menu once instead of ~3x. Stamp-path header-branding stays synchronous.
4 files changed
+23−6
adom-bridge-puppeteer-manifest.json+4−4@@ -1,10 +1,10 @@ { "manifest_version": 1, "name": "puppeteer",- "version": "2.0.2",- "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.2/adom-bridge-puppeteer-v2.0.2.zip",- "sha256": "3b6a9cb96999b11853e5aeb6c944f2d8815a51a2bb7b6b114260f295f46e579d",- "size": 637982,+ "version": "2.0.3",+ "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.3/adom-bridge-puppeteer-v2.0.3.zip",+ "sha256": "f4aad907a29dccb6bc70e9b3dbae07b21821e07bd5b87484e98abb4609181f79",+ "size": 638316, "verbPrefixes": [ "browser_", "desktop_recorder_",
src/BRIDGE_VERSION+1−1@@ -1 +1 @@-2.0.2+2.0.3
src/bridge.json+1−1@@ -2,7 +2,7 @@ "manifest_version": 1, "name": "puppeteer", "displayName": "Puppeteer (Chrome for Testing + Native)",- "version": "2.0.2",+ "version": "2.0.3", "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-desktop", "author": "Adom Inc.",
src/server.js+17@@ -3720,6 +3720,23 @@ async function updateWikiJumplist(session, sessionId, opts) { // wonkiness. One commit per (button, view), never a redundant one. const jlKey = `${appId}|${view || 'none'}|${pupSettings().jlViewTasks}|${pupSettings().jlCloseAll}`; if (session._wikiJumplistKey === jlKey) return;+ // v2.0.3: coalesce the jump-list settle churn. On open, the bare per-session appId and the+ // public->authed view each produce a distinct (appId|view) commit, so a single open committed the+ // menu ~3x. Debounce the callers that DON'T pass an explicit appId (the settle-driven refreshes):+ // schedule ONE commit after a short quiet window, by which point appId + view have settled and the+ // (appId|view) dedup above collapses it to a single commit. The stamp path passes opts.appId and+ // must stay synchronous (it brands the header right before creating the button, v1.9.61), so it is+ // exempt; the commit re-entry (opts._commit) is exempt so it can actually fire.+ if (!(opts && opts._commit) && !(opts && opts.appId)) {+ if (!session._jlCommitTimer) {+ session._jlCommitTimer = setTimeout(() => {+ session._jlCommitTimer = null;+ const s2 = sessions.get(sessionId);+ if (s2) updateWikiJumplist(s2, sessionId, { _commit: true }).catch(() => {});+ }, 1800);+ }+ return;+ } // v1.9.62: CLAIM the key before the await. Two callers (the pre-stamp brand and a timer-driven // refresh) can both compute the same key and both find it unset, so both commit — a redundant // CommitList that rebuilds the menu and can dismiss one the user is opening. Claiming up front