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
The dashboard err chip stops counting its own plumbing (John saw a red 10 err chip on a healthy dashboard after the window reopen). Both sources were self-inflicted 404s on the dashboard page: the badge preview endpoint now answers a transparent pixel while a freshly opened window has no composed overlay yet, and the bridge answers Chromes automatic favicon.ico probe with a redirect to the dashboard icon instead of a 404. The chip now only fires on real page errors
4 files changed
+20−7
adom-bridge-puppeteer-manifest.json+4−4@@ -1,10 +1,10 @@ { "manifest_version": 1, "name": "puppeteer",- "version": "2.0.93",- "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.93/adom-bridge-puppeteer-v2.0.93.zip",- "sha256": "e8fe4119aab0f41cfdd3782d38e97bc5b6d7f8e95a1b82f6277820c4c21ed5b6",- "size": 842892,+ "version": "2.0.94",+ "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.94/adom-bridge-puppeteer-v2.0.94.zip",+ "sha256": "10648d5464ef7489834d28baaf9c7e7a90e90bfa17c798f907483b2abdfd124c",+ "size": 843228, "verbPrefixes": [ "browser_", "desktop_recorder_",
src/BRIDGE_VERSION+1−1@@ -1 +1 @@-2.0.93+2.0.94
src/bridge.json+1−1@@ -2,7 +2,7 @@ "manifest_version": 1, "name": "puppeteer", "displayName": "Puppeteer (Chrome for Testing + Native)",- "version": "2.0.93",+ "version": "2.0.94", "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+14−1@@ -10953,7 +10953,20 @@ const server = http.createServer(async (req, res) => { // version → new URL → one refetch; between repaints the browser serves from cache (no blip). res.writeHead(200, { 'Content-Type': 'image/png', 'Cache-Control': 'public, max-age=3600' }); res.end(buf); return;- } catch (e) { res.writeHead(404); res.end(); return; }+ } catch (e) {+ // v2.0.94: a 1x1 transparent PNG instead of a 404. A freshly (re)opened window has no+ // composed overlay yet, and every such 404 landed in the dashboard page's OWN error+ // tracking — the red "N err" chip was counting its self-inflicted badge probes (John saw+ // "10 err" on a healthy dashboard). No badge is an empty image, not an error.+ res.writeHead(200, { 'Content-Type': 'image/png', 'Cache-Control': 'no-store' });+ res.end(Buffer.from('iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAADUlEQVR42mNkYPhfDwAChwGA60e6kgAAAABJRU5ErkJggg==', 'base64')); return;+ }+ }+ if (pathname === '/favicon.ico') {+ // v2.0.94: Chrome probes /favicon.ico on every bridge-served page; the 404 polluted the+ // dashboard's err chip. Serve the dashboard icon.+ res.writeHead(302, { Location: '/dashboard/icon.svg', 'Cache-Control': 'public, max-age=86400' });+ res.end(); return; } if (pathname === '/dashboard' || pathname === '/dashboard/') { res.writeHead(200, { 'Content-Type': 'text/html; charset=utf-8' });