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
v1.9.20: regenerate category icons with BMP frames so the shell RelaunchIconResource loader paints them instead of the white fallback
5 files changed
+23−12
CHANGELOG.md+11@@ -1,5 +1,16 @@ # Changelog — Adom Desktop Puppeteer Bridge +## 1.9.20 — 2026-07-20 — Category icons paint now: ICO frames must be BMP, not PNG++The 1.9.19 category icons applied cleanly (AD reported the stamp and registration OK) but the+taskbar painted the generic white-page fallback. Root cause: the ICOs were written with+PNG-compressed frames (PIL's default), and the shell path that resolves a window's+RelaunchIconResource cannot parse them, so it fell back. AD's own HICON loading handles PNG frames,+which is why every API response said success while the button stayed white. Regenerated all five+category icons with classic BMP frames (bitmap_format="bmp"; pure-BMP verified, no PNG signatures)+under new filenames per the icon-cache rule. The old hand-built adom-pup-browser3.ico that always+painted is BMP-frame, which corroborates the diagnosis.+ ## 1.9.19 — 2026-07-20 — One session one window, category icons, and no emoji anywhere Three things, in the order John asked for them.
adom-bridge-puppeteer-manifest.json+5−5@@ -1,10 +1,10 @@ { "manifest_version": 1, "name": "puppeteer",- "version": "1.9.19",- "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.19/adom-bridge-puppeteer-v1.9.19.zip",- "sha256": "8964a74ad67104723bcf6a7e08931455118242d468798c807eb63926470b9474",- "size": 306883,+ "version": "1.9.20",+ "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.20/adom-bridge-puppeteer-v1.9.20.zip",+ "sha256": "42cdff241627c19594accd21e5be6cdf08ab7600d2cbbd53037b00a1c7e9d0a8",+ "size": 289850, "verbPrefixes": [ "browser_", "desktop_recorder_",@@ -12,5 +12,5 @@ ], "healthEndpoint": "/status", "statusVerb": "browser_readiness",- "released_at": "2026-07-20T01:30:00Z"+ "released_at": "2026-07-20T02:00:00Z" }
src/BRIDGE_VERSION+1−1@@ -1 +1 @@-1.9.19+1.9.20
src/bridge.json+1−1@@ -2,7 +2,7 @@ "manifest_version": 1, "name": "puppeteer", "displayName": "Puppeteer (Chrome for Testing + Native)",- "version": "1.9.19",+ "version": "1.9.20", "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+5−5@@ -1716,11 +1716,11 @@ let _jumplistSupported = null; // null = unprobed (desktop_set_window_jumplist // mixed stacked windows tabs spanning more than one category const PUP_ICON_DEFAULT = 'adom-pup-browser3.ico'; const PUP_CAT_ICONS = {- wiki: 'pup-cat-wiki1.ico',- 'wiki-in': 'pup-cat-wiki-in1.ico',- app: 'pup-cat-app1.ico',- web: 'pup-cat-web1.ico',- mixed: 'pup-cat-mixed1.ico',+ wiki: 'pup-cat-wiki2.ico',+ 'wiki-in': 'pup-cat-wiki-in2.ico',+ app: 'pup-cat-app2.ico',+ web: 'pup-cat-web2.ico',+ mixed: 'pup-cat-mixed2.ico', }; function classifyUrl(u) { try {