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
1.8.69: sized opens keep x/y (z-only re-assert), window-management default grant for real monitor enumeration
5 files changed
+28−14
CHANGELOG.md+12@@ -1,5 +1,17 @@ # Changelog — Adom Desktop Puppeteer Bridge +## 1.8.69 — 2026-07-15 — Sized opens keep their x/y (multi-monitor placement works); window-management granted++- The sized-open background re-assert was still the LEGACY PS park, which moves the window to 0,0+ sized-to-monitor — silently clobbering the caller's x/y/w/h (every sized open snapped back to+ the primary monitor's origin, making second-monitor placement impossible). It is now AD+ `state:'bottom' force:false` — z-order only, geometry untouched, user-held windows respected.+- `window-management` added to the permissive default grants so `getScreenDetails()` works inside+ pup pages (it used to hang forever on a CDP-suppressed permission prompt) — pup can now+ enumerate the REAL monitor layout from Chrome itself. Chrome sees monitors AD's+ `desktop_list_monitors` misses (ADOMGPU reports 1 monitor via AD but isExtended:true in Chrome;+ AD gap to file).+ ## 1.8.68 — 2026-07-15 — Park AFTER the page settles: the paint-raise happens invisibly off-screen Even with 1.8.67's re-asserts, the raise-then-re-bottom left a visible blip: another thread's
adom-bridge-puppeteer-manifest.json+4−4@@ -1,10 +1,10 @@ { "manifest_version": 1, "name": "puppeteer",- "version": "1.8.68",- "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.8.68/adom-bridge-puppeteer-v1.8.68.zip",- "sha256": "32860c35a5e99d70eeb4bf0af118f7badbbe8a086fff939deadb66dadbe664ea",- "size": 173547,+ "version": "1.8.69",+ "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.8.69/adom-bridge-puppeteer-v1.8.69.zip",+ "sha256": "a39875c6d23ad5630a4678096b2ea1912f849f7f7a4269ef6b89846889266d8b",+ "size": 173714, "verbPrefixes": [ "browser_", "desktop_recorder_",
src/BRIDGE_VERSION+1−1@@ -1 +1 @@-1.8.68+1.8.69
src/bridge.json+1−1@@ -2,7 +2,7 @@ "manifest_version": 1, "name": "puppeteer", "displayName": "Puppeteer (Chrome for Testing + Native)",- "version": "1.8.68",+ "version": "1.8.69", "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.", "homepage": "https://wiki.adom.inc/adom/adom-desktop", "author": "Adom Inc.",
src/server.js+10−8@@ -1360,6 +1360,9 @@ async function closeRestoredLeftoverTabs(browser, keepPage) { // clipboard-sanitized-write) only drops itself — the rest still land. Opt-out via // strictPermissions:true on browser_open_window for an untrusted site you're auditing. const PERMISSIVE_DEFAULT_PERMISSIONS = [+ // v1.8.69: window-management → getScreenDetails() works (multi-monitor enumeration from+ // inside the page; without the grant it hangs on a CDP-suppressed permission prompt).+ { name: 'window-management', setting: 'granted' }, { name: 'clipboard-read', setting: 'granted' }, { name: 'clipboard-write', setting: 'granted' }, { name: 'clipboard-sanitized-write', setting: 'granted' },@@ -3817,16 +3820,15 @@ const server = http.createServer(async (req, res) => { // innerWidth/innerHeight deterministic, which is what fullPage/element shots need. try { await session.page.setViewport({ width: Math.round(w), height: Math.round(h), deviceScaleFactor: Number(args.deviceScaleFactor) || 1 }); } catch (e) {} }- // v1.8.51: re-assert background ONLY after an explicit sizing call (CDP- // setWindowBounds can re-activate the window). For a plain open this re-assert is- // GONE — it duplicated the launch park and was one more thing that could fight a- // user's early taskbar click. The respectUser foreground check keeps even the sized- // path from yanking a window the user has up.+ // v1.8.69: re-assert background after an explicit sizing call — Z-ORDER ONLY.+ // The old call here was the legacy osBackgroundWindowByPid, whose PS park MOVES the+ // window to 0,0 sized-to-monitor — silently clobbering the exact x/y/w/h the caller+ // just asked for (every sized open snapped back to the primary monitor's origin,+ // which broke placing windows on a second monitor). AD state:'bottom' with+ // force:false touches nothing but z, and respects a user-held window. if (!foreground && sized) { try {- const be = browsers.get(args.profile);- if (be && be.browser) be.browser._bgResult = osBackgroundWindowByPid(be.browser._detachedPid, be.browser._cdpPort, be.browser._priorForeground, true);- else osSendWindowToBack(args.profile);+ await chrome.adCommand('desktop_set_window_state', { titleContains: `(session: ${sessionId}`, state: 'bottom', force: false }, { timeoutMs: 5000 }); } catch (e) {} } // v1.8.26: record whether this window is meant to be on screen — gates every