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
One flash per open operation (John: 'did you orange flash them twice? ... i had to go click all of them again to expire the orange flash' — measured on the 10-window stress test, every heavy site double-flashed). The launch path flashes instantly and records _openFlashDone; the open handler now CONSUMES that marker and skips its own post-load flash, so suppression is scoped to the OPERATION instead of a 5s time debounce that any heavy site (YouTube, Maps) outruns — the second orange landed AFTER John had clicked, forcing him to re-click every window. Every flash now logs '[flash] <session> (launch|auto)' so a double-flash can never hide in silence again. Also: the complete window-UX doctrine from today's placement war (10 laws: background=behind never off-screen, per-window unconditional park, windowState normal before bounds, re-assert, no -32000 defaults, one flash per operation, no terminal blips ever, atomic reveal, foreground gated on the user's words, patch-the-code-that-runs/prove-on-glass) is now dev-skills/pup-bridge-dev SKILL.md law.
4 files changed
+17−8
adom-bridge-puppeteer-manifest.json+4−4@@ -1,10 +1,10 @@ { "manifest_version": 1, "name": "puppeteer",- "version": "1.9.139",- "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.139/adom-bridge-puppeteer-v1.9.139.zip",- "sha256": "192fd9e9ec585a84d5f1e6211fcc8d99ea49ea3d2041b1374e9efd4c557bad86",- "size": 395138,+ "version": "1.9.140",+ "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.140/adom-bridge-puppeteer-v1.9.140.zip",+ "sha256": "26f224fa850c670c8994cec959b132fd49638833bcf77d79a2e3cf74e33564e1",+ "size": 395547, "verbPrefixes": [ "browser_", "desktop_recorder_",
src/BRIDGE_VERSION+1−1@@ -1 +1 @@-1.9.139+1.9.140
src/bridge.json+1−1@@ -2,7 +2,7 @@ "manifest_version": 1, "name": "puppeteer", "displayName": "Puppeteer (Chrome for Testing + Native)",- "version": "1.9.139",+ "version": "1.9.140", "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+11−2@@ -4614,6 +4614,13 @@ function authSteerHint(url) { return ' 🔑 AUTH URL DETECTED: pup is the ANONYMOUS SANDBOXED browser — its profiles are disposable, so a login done here is easily lost (next fresh window = signed out), and it must not become the home of the user\'s identity. For signing the USER into their accounts prefer: (a) abe / nbrowser_* — their REAL browser where sessions + password manager already live, or (b) AD-core desktop_open_url — a plain native OS launch of their default browser (zero automation machinery; ideal for OAuth flows that just need the user to click Approve). Continue in pup ONLY for throwaway/test accounts or when the flow explicitly needs an anonymous context.'; } const _flashState = new Map(); // sessionId -> last flash ts+// v1.9.140 (John: 'did you orange flash them twice? ... i had to go click all of them again') —+// ONE FLASH PER OPEN, operation-scoped. The launch path flashes instantly, and the open handler+// used to flash again after the real URL loaded; the 5s TIME debounce between them is outrun by+// any heavy site (YouTube/Maps load >5s), so every slow page double-flashed — and a second orange+// AFTER the user already clicked forces them to click every window again. A consumed-once marker+// scopes suppression to the OPEN OPERATION regardless of load time.+const _openFlashDone = new Map(); // sessionId -> ts of the launch flash for the current open function scheduleAutoFlash(session, opts) { opts = opts || {}; if (process.platform !== 'win32' || !session || !session._sessionId) return;@@ -4622,6 +4629,7 @@ function scheduleAutoFlash(session, opts) { const now = Date.now(); if (now - (_flashState.get(key) || 0) < 5000) return; // coalesce the burst _flashState.set(key, now);+ console.log(`[flash] "${key}" (auto)`); // v1.9.140: every flash logs, so a double-flash can never hide again flashViaAD(session._sessionId, {}); // fire-and-forget (async → AD desktop_flash_window) } @@ -5406,7 +5414,7 @@ async function launchSession(sessionId, url, { freshProfile = false, profile, st // real URL's domcontentloaded, which for heavy sites is another 1–3s. Set _flashState so // the open handler's later scheduleAutoFlash debounces (no double flash). Fire-and-forget. if (!foreground && !silent && process.platform === 'win32') {- try { _flashState.set(sessionId, Date.now()); flashViaAD(sessionId, {}); } catch (e) {}+ try { _flashState.set(sessionId, Date.now()); _openFlashDone.set(sessionId, Date.now()); console.log(`[flash] "${sessionId}" (launch)`); flashViaAD(sessionId, {}); } catch (e) {} } if (url) {@@ -6882,7 +6890,8 @@ const server = http.createServer(async (req, res) => { // (already on screen) or suppressed. Also stamp the first agent update. if (session) { recordAgentUpdate(session, 'browser_open_window', args, session.activeTabId);- if (!foreground) scheduleAutoFlash(session, { silent: !!args.silent });+ // v1.9.140: the launch path already flashed this open — consume the marker and skip.+ if (!foreground && !_openFlashDone.delete(sessionId)) scheduleAutoFlash(session, { silent: !!args.silent }); } // v1.8.53: badge timing moved into the park (launchSession) — it fires the moment the // park verdict lands instead of blind 1.5s/3.5s timers. This is only a fallback for