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.26: seed authed state at session creation so the first taskbar icon is the signed-in variant, since Windows latches button icons
5 files changed
+25−7
CHANGELOG.md+11@@ -1,5 +1,16 @@ # Changelog — Adom Desktop Puppeteer Bridge +## 1.9.26 — 2026-07-20 — Signed-in icon applies on the FIRST stamp (Windows latches button icons)++Proven live: ex-wikiin stamped and registered icon=wiki-in, yet its taskbar button kept the plain+book. Windows latches a button's icon at window creation; later in-place re-stamps often do not+repaint. Fix: a session launching on the authed wiki profile is authed-intent, so _wikiAuthed is+seeded at session creation, BEFORE the first identity stamp - the first icon is already+book-plus-person. The post-open auth probe still corrects the flag and tab glyph if the ~30-day+session expired. Remaining known gap (AD ask): a category flip on a LIVE window (wiki to mixed by+adding a tab) re-stamps correctly but the button may hold the old icon until the window recreates;+needs an AD-side force-refresh of the taskbar tile.+ ## 1.9.25 — 2026-07-20 — Signed-in wiki icon is now unmistakably different (book + person) John called it: the outline-vs-solid book distinction technically existed but read identical at
adom-bridge-puppeteer-manifest.json+5−5@@ -1,10 +1,10 @@ { "manifest_version": 1, "name": "puppeteer",- "version": "1.9.25",- "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.25/adom-bridge-puppeteer-v1.9.25.zip",- "sha256": "c19183bbf7f7fb7dccff981d9e647c44e5197d7e65ea7f55ca1135928c9a79aa",- "size": 280999,+ "version": "1.9.26",+ "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.26/adom-bridge-puppeteer-v1.9.26.zip",+ "sha256": "ff4d4034a582fbf63a0ec1c5228c8910ba4246cd43a31b7252068f21265f8a25",+ "size": 281278, "verbPrefixes": [ "browser_", "desktop_recorder_",@@ -12,5 +12,5 @@ ], "healthEndpoint": "/status", "statusVerb": "browser_readiness",- "released_at": "2026-07-20T04:15:00Z"+ "released_at": "2026-07-20T04:45:00Z" }
src/BRIDGE_VERSION+1−1@@ -1 +1 @@-1.9.25+1.9.26
src/bridge.json+1−1@@ -2,7 +2,7 @@ "manifest_version": 1, "name": "puppeteer", "displayName": "Puppeteer (Chrome for Testing + Native)",- "version": "1.9.25",+ "version": "1.9.26", "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+7@@ -3828,6 +3828,13 @@ async function launchSession(sessionId, url, { freshProfile = false, profile, st // Create the session with this page as its first tab. const session = createSession(profileName);+ // v1.9.26: sessions on the authed wiki profile are authed-INTENT — seed the flag NOW, before+ // the first identity stamp, so the FIRST taskbar icon is already the signed-in one. Windows+ // LATCHES a button's icon at creation and in-place re-stamps often do not repaint (proven live:+ // ex-wikiin registered icon=wiki-in yet kept the plain book), so correcting the icon later is+ // unreliable — the first stamp must be right. The real auth probe still runs after open and+ // corrects the flag (and the tab glyph) if the ~30-day session actually expired.+ if (profileName === WIKI_AUTH_PROFILE) session._wikiAuthed = true; // v1.8.16: stamp the declared owner (advisory thread/task label) at create. if (owner) session.owner = owner; // v1.6.3+: stash the per-session downloadPath BEFORE attachTab — attachTab