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
v2.0.358: Split the log ring in two (issue #80): the loop radar emitted a summary every minute into the same fixed buffer as the events, so an hour of history was mostly cadence and any real event was evicted, which is why a thread investigating vanished tabs found nothing to correlate. Events now get a 2000-line ring of their own and reclaim, recovery, migrate, park and dialog lines are captured.
5 files changed
+36−9
adom-bridge-puppeteer-manifest.json+5−5@@ -1,10 +1,10 @@ { "manifest_version": 1, "name": "puppeteer",- "version": "2.0.357",- "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.357/adom-bridge-puppeteer-v2.0.357.zip",- "sha256": "fb9027032086fcf4b2d2a22f94b589017db7e68c0255de0533e717cb5488b390",- "size": 1527232,+ "version": "2.0.358",+ "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.358/adom-bridge-puppeteer-v2.0.358.zip",+ "sha256": "49c098174e496d231ebb2d14985e63ffc22d145992884e6ca825ad36f589612e",+ "size": 1527745, "verbPrefixes": [ "browser_", "desktop_recorder_",@@ -12,5 +12,5 @@ ], "healthEndpoint": "/status", "statusVerb": "browser_readiness",- "released_at": "2026-08-27T13:59:29.821308Z"+ "released_at": "2026-08-27T14:41:00.997587Z" }
package.json+1−1@@ -1,6 +1,6 @@ { "slug": "pup-bridge",- "version": "2.0.357",+ "version": "2.0.358", "type": "app", "description": "The pup SKILL PACK \u2014 the AI skills that teach a cloud/container AI how to drive the Adom Desktop Puppeteer (pup) bridge (browser_* verbs): the everyday `pup` skill plus focused sub-skills for windows/sessions/tabs, screenshots+recording, browsers+Chrome install, and driving the Adom wiki. Installs into ~/.claude/skills + ~/.codex/skills. DOCS ONLY \u2014 this is NOT the bridge runtime. The bridge itself (the Node program that drives the browser) runs on the DESKTOP: Adom Desktop bundles it and auto-installs/updates it, and it's published separately on the Releases tab as adom-bridge-puppeteer-v<ver>.zip. The pkg version is kept in lockstep with the Release version so the page's max version row always carries BOTH a pkg tarball (skills) and a runtime zip (bridge) \u2014 a skills-only or runtime-only bump on the top row breaks constraint installs. TL;DR: pkg install = the skills for your AI; the bridge = the Release zip, which Adom Desktop manages for you.", "keywords": [
src/BRIDGE_VERSION+1−1@@ -1 +1 @@-2.0.357+2.0.358
src/bridge.json+1−1@@ -2,7 +2,7 @@ "manifest_version": 1, "name": "puppeteer", "displayName": "Puppeteer (Chrome for Testing + Native)",- "version": "2.0.357",+ "version": "2.0.358", "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+28−1@@ -47,7 +47,33 @@ setInterval(() => { } catch (e) {} }, 60000); const _logRing = [];-{ const _orig = console.log.bind(console); console.log = (...a) => { try { const t = a.map(x => typeof x === 'string' ? x : JSON.stringify(x)).join(' '); if (/^\[(hwnd|birth|focus|foreground|caption|screenshot|settings|annotate|launch|loops|visibility|health)\]/.test(t)) { _logRing.push(new Date().toISOString().slice(11, 23) + ' ' + t.slice(0, 300)); if (_logRing.length > 300) _logRing.shift(); } } catch (e) {} _orig(...a); }; } // v2.0.310: in-process Win32 (SetProp/GetProp/EnumWindows), no PowerShell+// v2.0.358 (issue #80). TWO RINGS, because one ring made pup undiagnosable at the exact moment+// somebody needed it. The loop radar emits a [loops] summary EVERY MINUTE, and it shared this ring+// with the event lines, so a 60-line window of history was mostly loop noise and any real event+// (a reclaim, a birth, a tab moving) was evicted within the hour. A thread investigating vanished+// tabs read the log, found nothing it could correlate, and reported "bridge_log_read returned an+// empty output" — the log was not empty, the evidence had been pushed out by my own telemetry.+// Loop summaries are periodic and low-value per line; events are rare and high-value. They do not+// belong in the same fixed-size buffer. Events now get a much deeper ring of their own.+const _loopRing = [];+{+ const _orig = console.log.bind(console);+ const EVENT_RE = /^\[(hwnd|birth|focus|foreground|caption|screenshot|settings|annotate|launch|visibility|health|reclaim|recovery|migrate|park|dialog|tab)\]/;+ console.log = (...a) => {+ try {+ const t = a.map(x => typeof x === 'string' ? x : JSON.stringify(x)).join(' ');+ const stamped = new Date().toISOString().slice(11, 23) + ' ' + t.slice(0, 300);+ if (/^\[loops\]/.test(t)) {+ _loopRing.push(stamped);+ if (_loopRing.length > 60) _loopRing.shift(); // one per minute: an hour of cadence+ } else if (EVENT_RE.test(t)) {+ _logRing.push(stamped);+ if (_logRing.length > 2000) _logRing.shift(); // events are what an investigation needs+ }+ } catch (e) {}+ _orig(...a);+ };+} // v2.0.310: in-process Win32 (SetProp/GetProp/EnumWindows), no PowerShell const os = require('os'); const { execSync, execFileSync, execFile } = require('child_process'); // v1.8.29: run a PowerShell script file with NO console window (windowsHide) and no cmd@@ -8689,6 +8715,7 @@ function statusCore() { enumWindows: { total: _enumCalls, lastMin: (Date.now() - _enumWindow.at < 60000 ? _enumWindow.n : 0) }, win32: { inProcess: win32.available(), why: win32.why() }, // v2.0.310: koffi loaded? (else PowerShell fallback) log: _logRing.slice(-120),+ loops: _loopRing.slice(-10), // #80: cadence kept separate so it cannot evict the events loops: loopReport(), win32Calls: win32.stats ? win32.stats() : {}, // the CURRENT identity mode, so a test harness asserts against what pup IS, not an assumption