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.360: Retry the adopted-window title lookup (follow-up to 2.0.357): the OS window title lags the DOM title, so a single immediate pass missed every adoption, and the disruption notice no longer depends on tagging succeeding.
5 files changed
+22−10
adom-bridge-puppeteer-manifest.json+5−5@@ -1,10 +1,10 @@ { "manifest_version": 1, "name": "puppeteer",- "version": "2.0.359",- "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.359/adom-bridge-puppeteer-v2.0.359.zip",- "sha256": "0d338c53deaee32004f10cc96b290d6ec142db67cc1259ddcad1a89cb178fd0a",- "size": 1528884,+ "version": "2.0.360",+ "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.360/adom-bridge-puppeteer-v2.0.360.zip",+ "sha256": "d7dc88b7e9e50bd22fcf4054d67b23be9ac11031ddf3c6a4f946072cbad08796",+ "size": 1529214, "verbPrefixes": [ "browser_", "desktop_recorder_",@@ -12,5 +12,5 @@ ], "healthEndpoint": "/status", "statusVerb": "browser_readiness",- "released_at": "2026-08-27T15:53:29.568238Z"+ "released_at": "2026-08-27T15:55:44.549687Z" }
package.json+1−1@@ -1,6 +1,6 @@ { "slug": "pup-bridge",- "version": "2.0.359",+ "version": "2.0.360", "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.359+2.0.360
src/bridge.json+1−1@@ -2,7 +2,7 @@ "manifest_version": 1, "name": "puppeteer", "displayName": "Puppeteer (Chrome for Testing + Native)",- "version": "2.0.359",+ "version": "2.0.360", "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−2@@ -9170,7 +9170,17 @@ async function reclaimUnmanagedWindows() { // be recovered without guessing, and the tag then survives every later handle loss. try { const _mark = `${TITLE_LABEL}: ${newId}`;- const _hit = win32.findChromeWindowByTitle(_mark);+ // v2.0.360: RETRY. 2.0.357 looked exactly once, immediately after writing the title, and+ // missed every time ("could not find its OS window by title" on all three adoptions in+ // one restart, found in the event log the moment #80's ring fix made events visible).+ // The DOM title is set synchronously by page.evaluate; the OS WINDOW title is updated by+ // Chrome a frame or two later, so a single in-process EnumWindows pass reliably runs+ // before the string it is searching for exists. Poll briefly instead of guessing a sleep.+ let _hit = null;+ for (let _i = 0; _i < 12 && !_hit; _i++) {+ _hit = win32.findChromeWindowByTitle(_mark) || null;+ if (!_hit) await new Promise(r => setTimeout(r, 60));+ } if (_hit && _hit.hwnd) { ns._hwnd = Number(_hit.hwnd); await tagWindowSession(_hit.hwnd, newId);@@ -9178,11 +9188,13 @@ async function reclaimUnmanagedWindows() { // #80: an adopted window is one pup found unowned. Whichever thread it USED to belong to // is not addressable any more, so the notice goes on the new session and the janitor // queue carries the broadcast, because the original owner cannot be reached by name.- noteSessionDisruption(ns, `pup adopted this window after a restart: it was running but no session owned it. Its original AI thread, if any, has lost its handle to it and must re-open. Nothing was closed.`); } else { console.log(`[reclaim] "${newId}": could not find its OS window by title — it will stay untagged and unresolvable until a later resolve succeeds`); } } catch (e) { console.log(`[reclaim] "${newId}": tagging failed: ${e.message}`); }+ // #80: the notice is about the ADOPTION, not about whether tagging succeeded, so it is set+ // unconditionally. Tying it to the tag meant a failed tag also swallowed the explanation.+ noteSessionDisruption(ns, `pup adopted this window after a restart: it was running but no session owned it. Its original AI thread, if any, has lost its handle to it and must re-open. Nothing was closed.`); console.log(`[reclaim] UNMANAGED window on "${profileName}" (${group.length} tab(s)) adopted as "${newId}" — ${(u || '').slice(0, 60)}`); refreshWindowChrome(ns, newId).catch(() => {}); // v1.9.202: an ADOPTED window also needs its badge — refreshWindowChrome is gated off under