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
Make the 2.0.34 set-diff birth capture actually resolve under concurrency: widen the off-screen birth spacing from 40px to 220px so disambiguating concurrent births by nearest-birthLeft is unambiguous against Chrome placement jitter (the 18px tolerance was too tight and left every concurrent birth AMBIGUOUS with nothing stamped; 60px had been too loose and cross-wired). New windows are identified by set-diff, then the one nearest my unique birthLeft is mine
4 files changed
+11−8
adom-bridge-puppeteer-manifest.json+4−4@@ -1,10 +1,10 @@ { "manifest_version": 1, "name": "puppeteer",- "version": "2.0.34",- "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.34/adom-bridge-puppeteer-v2.0.34.zip",- "sha256": "4ac706f11de9f032a54c318a793c9a1c5c120db56233ac08068181f0c28b072f",- "size": 642959,+ "version": "2.0.35",+ "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.35/adom-bridge-puppeteer-v2.0.35.zip",+ "sha256": "8d41846c24fe964829a46c1cbfaee90fffca54e08d72a2d85ff86fd24f2c9487",+ "size": 643107, "verbPrefixes": [ "browser_", "desktop_recorder_",
src/BRIDGE_VERSION+1−1@@ -1 +1 @@-2.0.34+2.0.35
src/bridge.json+1−1@@ -2,7 +2,7 @@ "manifest_version": 1, "name": "puppeteer", "displayName": "Puppeteer (Chrome for Testing + Native)",- "version": "2.0.34",+ "version": "2.0.35", "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+5−2@@ -7520,7 +7520,7 @@ async function createPageInNewWindow(browser, profileName) { // same-profile window is unambiguous. After park it is maximized + shares the parked rect with its // siblings, which is why the width-wiggle could never tell them apart. Captured here, stashed on the // page, trusted by resolveSessionHwndByBounds. This is the fix for multi-window profiles (adom-you).- const birthLeft = -32000 - ((_birthSeq++ % 300) * 40);+ const birthLeft = -32000 - ((_birthSeq++ % 60) * 220); // v2.0.35: 220px apart (was 40) so set-diff's nearest-match can't cross-wire adjacent births try { const before = new Set(await browser.pages()); // v2.0.34: snapshot existing OS window handles BEFORE creating, so the SET-DIFF below identifies@@ -7563,9 +7563,12 @@ async function createPageInNewWindow(browser, profileName) { const newOff = rows.filter(r => r.T < -10000 && !_beforeHwnds.has(Number(r.h)) && !hwndOwnedByOtherSession(r.h, null)); if (newOff.length === 1) picked = newOff[0].h; else if (newOff.length > 1) {+ // v2.0.35: pick the NEW off-screen window NEAREST my birthLeft (across DPI scales). Births+ // are 220px apart now, so nearest is unambiguous against Chrome's small placement jitter;+ // no hard tolerance to be too-tight (18px failed) or too-loose (60px cross-wired). let best = null, bestErr = 1e9; for (const r of newOff) for (const sc of [1, 1.25, 1.5, 1.75, 2]) { const e = Math.abs(r.L - Math.round(birthLeft * sc)); if (e < bestErr) { bestErr = e; best = r.h; } }- if (best && bestErr <= 18) picked = best; // tight: unique birthLeft, no adjacent collision+ if (best && bestErr <= 140) picked = best; } if (!picked) await new Promise(r => setTimeout(r, 120)); }