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.11: consume AD fixes - loopback desktop_caption with expiresInMs, relaunchCommand trio brands the jump-list header, retire in-page toast
5 files changed
+61−47
CHANGELOG.md+19@@ -1,5 +1,24 @@ # Changelog — Adom Desktop Puppeteer Bridge +## 1.9.11 — 2026-07-19 — OS captions live, jump-list header branded, in-page toast retired++AD shipped all four asks; pup now consumes them.+- **desktop_caption on the loopback API (AD 1.9.144).** The earlier silent no-op was a wider AD hole+ than "relay-only": ~90 inline verbs matched only their BARE names, and the CLI strips the+ `desktop_` prefix client-side — which is exactly why a CLI test passed while pup's identical call+ did nothing. Both spellings work now. Fixed pup's arg name too: it is `expiresInMs`, NOT `duration`.+- **In-page toast RETIRED.** With a real OS surface available, pup should not inject DOM into the+ user's page. Captions are also the only feedback that survives the window teardown mid-switch.+- **Jump-list header icon (AD 1.9.141).** Not a registry fix — there is no ApplicationIcon value on+ AUMID keys and the registry cannot brand the header at all. The header obeys the window's Relaunch*+ TRIO, and Windows ignores RelaunchIconResource unless RelaunchCommand is ALSO set. stampPupIdentity+ now passes relaunchCommand (a real `browser_focus_window` for that session, carrying a+ foregroundReason since the raise gate demands one, with Windows-argv-escaped quotes).+- **Jump-list cmd flash (AD 1.9.143)** needed no pup change (AD interposes a GUI-subsystem shim);+ pup re-sets jump lists at every open/navigate, so pre-1.9.143 lists heal automatically.+- **Log rotation:** answered, bounded. Per-spawn `<name>.log` truncates on respawn; the appended+ `<name>.ad.log` is hard-capped (trimmed to newest 64 KB at 128 KB). No janitor needed on pup's side.+ ## 1.9.10 — 2026-07-19 — In-page toast feedback (desktop_caption is relay-only) + branding race fix Root-caused why the 1.9.9 captions never appeared: AD's loopback direct API — the path bridges use
adom-bridge-puppeteer-manifest.json+5−5@@ -1,10 +1,10 @@ { "manifest_version": 1, "name": "puppeteer",- "version": "1.9.10",- "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.10/adom-bridge-puppeteer-v1.9.10.zip",- "sha256": "12abde61276e5abb71ab88570348c6d235e9755c8828b5be4ff98aad1b66051f",- "size": 217534,+ "version": "1.9.11",+ "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.11/adom-bridge-puppeteer-v1.9.11.zip",+ "sha256": "10d0811ba5c5ce4e13f4429327702cb54701f1a94e003b7ecc58c9d3a1b35700",+ "size": 217687, "verbPrefixes": [ "browser_", "desktop_recorder_",@@ -12,5 +12,5 @@ ], "healthEndpoint": "/status", "statusVerb": "browser_readiness",- "released_at": "2026-07-19T22:35:00Z"+ "released_at": "2026-07-19T23:00:00Z" }
src/BRIDGE_VERSION+1−1@@ -1 +1 @@-1.9.10+1.9.11
src/bridge.json+1−1@@ -2,7 +2,7 @@ "manifest_version": 1, "name": "puppeteer", "displayName": "Puppeteer (Chrome for Testing + Native)",- "version": "1.9.10",+ "version": "1.9.11", "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+35−40@@ -1694,6 +1694,17 @@ let _jumplistSupported = null; // null = unprobed (desktop_set_window_jumplist // Windows' shell + AD's HICON cache key by path (stale-tile risk otherwise). Future home for // the master art: the Adom brand-icons wiki repo; for now the pup repo owns it. function pupIconPath() { return path.join(__dirname, 'icons', 'adom-pup-browser3.ico'); }+// v1.9.11: the RelaunchCommand half of the Relaunch* trio (see stampPupIdentity) — Windows will+// not honor RelaunchIconResource for the jump-list header row unless RelaunchCommand is set too.+// It is also literally what a header click / taskbar PIN launches, so it must genuinely refocus+// THIS session. browser_focus_window is gated (foreground_reason_required), so we supply an+// honest reason: a header/pin click IS the user asking to see the window. Inner quotes are+// BACKSLASH-escaped because this is a Windows command line (same argv trap as jump-list args).+function pupRelaunchCommand(sessionId) {+ const cli = path.join(process.env.LOCALAPPDATA || path.join(os.homedir(), 'AppData', 'Local'), 'Adom Desktop', 'adom-desktop-cli.exe');+ const payload = JSON.stringify({ sessionId, foregroundReason: 'user clicked the Adom Pup taskbar header or pinned launcher' }).replace(/"/g, '\\"');+ return `"${cli}" browser_focus_window "${payload}"`;+} function _isUnknownVerb(r, raw) { return /unknown (desktop )?command|unknown verb/i.test(((r && r.error) || '') + ' ' + (raw || '')); } async function ensurePupIdentityRegistered() { if (process.platform !== 'win32' || _identitySupported === false) return false;@@ -1728,6 +1739,16 @@ async function stampPupIdentity(sessionId) { const r = await chrome.adCommand('desktop_set_window_identity', { titleContains: `(session: ${sessionId}`, cacheKey: `pup-${sessionId}`, appId: pupSettings().taskbarGrouping === 'grouped' ? PUP_APP_ID : `${PUP_APP_ID}.${sessionId}`, displayName: PUP_DISPLAY_NAME, iconPath: pupIconPath(),+ // v1.9.11 (AD ≥1.9.141): brand the taskbar RIGHT-CLICK MENU HEADER row (it showed the+ // chrome.exe icon for months). There is NO "ApplicationIcon" registry value on AUMID keys+ // and the registry cannot brand the header at all — the header obeys the window's+ // Relaunch* property TRIO, and Windows IGNORES RelaunchIconResource unless RelaunchCommand+ // is ALSO set. So we must pass a real relaunch command. It doubles as what a header click+ // or a taskbar PIN launches, so it has to genuinely refocus THIS session: browser_focus_window+ // carries a foregroundReason (the raise gate refuses without one, and a header click IS a+ // real user request to see the window). Quotes are backslash-escaped for Windows argv —+ // same trap that made jump-list clicks no-op in 1.9.9.+ relaunchCommand: pupRelaunchCommand(sessionId), }, { timeoutMs: 6000 }); const raw = r && (typeof r.output === 'string' ? r.output : JSON.stringify(r.output || '')); if ((r && r.success === false) || _isUnknownVerb(r, raw)) {@@ -2068,47 +2089,24 @@ function appIconReprimand(url, hadFavicon) { // relaunches the browser under the other cookie jar and takes several seconds, so WITHOUT this a // click felt like nothing happened at all. Same `id` on every call so the start caption is // REPLACED by the result caption instead of stacking. Best-effort; never throws.-async function wikiCaption(text, duration) {+async function wikiCaption(text, expiresInMs) { try {- // v1.9.10: LOG the result — this call failed silently for a whole session because AD's- // loopback direct API does NOT expose desktop_caption (relay-only verb; confirmed live:- // "'desktop_caption' is not a built-in desktop verb"). Filed with AD; the moment it ships- // on the direct API this starts working with no pup change. Until then the in-PAGE toast- // (wikiToast) is the user-visible feedback.+ // v1.9.11: AD ≥1.9.144 exposes desktop_caption on the LOOPBACK direct API (the path bridges+ // use). Before that it was relay-only — ~90 inline verbs matched only their BARE names, and+ // the CLI strips the `desktop_` prefix client-side, which is exactly why a CLI test "worked"+ // while pup's identical call silently no-op'd. Both spellings are accepted now.+ // NOTE the arg is `expiresInMs` (NOT `duration`) — default 30000, max 600000.+ // This replaced the in-page DOM toast: with a real OS surface available, pup should not be+ // injecting elements into the user's page. const r = await chrome.adCommand('desktop_caption', {- text, duration, id: 'pup-wiki-view', position: 'bottom', size: 'medium',+ text, expiresInMs, id: 'pup-wiki-view', position: 'bottom', size: 'medium', }, { timeoutMs: 4000 }); const raw = r && (typeof r.output === 'string' ? r.output : JSON.stringify(r.output || r || '')); if (!r || (r.success === false) || /not a built-in desktop verb|unknown/i.test(raw || '')) {- console.log('[wiki] desktop_caption unavailable on this AD direct API (expected pre-fix) — in-page toast is the visible feedback');- } else {- console.log('[wiki] desktop_caption shown');+ console.log(`[wiki] desktop_caption FAILED (AD <1.9.144?) — ${(raw || 'no response').slice(0, 120)}`); } } catch (e) {} }-// v1.9.10: in-PAGE toast — pup-owned visual feedback that needs NO AD verb. A fixed-position-// pill injected into the page (top-center, Adom dark teal, auto-fade). Used by the wiki view-// toggle to confirm the switch IN the very window the user is now looking at. Idempotent per-// call (replaces any prior toast). Best-effort; never throws.-async function wikiToast(page, text, ms = 6000) {- try {- await page.evaluate((t, dur) => {- try {- const old = document.getElementById('__pup_wiki_toast'); if (old) old.remove();- const d = document.createElement('div');- d.id = '__pup_wiki_toast';- d.textContent = t;- d.style.cssText = 'position:fixed;top:18px;left:50%;transform:translateX(-50%);z-index:2147483647;' +- 'background:#0b2325;color:#e8fbfa;border:1px solid #14b8a6;border-radius:999px;' +- 'padding:10px 22px;font:600 15px/1.4 system-ui,sans-serif;box-shadow:0 6px 24px rgba(0,0,0,.45);' +- 'opacity:0;transition:opacity .25s ease;pointer-events:none;max-width:80vw;text-align:center';- (document.body || document.documentElement).appendChild(d);- requestAnimationFrame(() => { d.style.opacity = '1'; });- setTimeout(() => { try { d.style.opacity = '0'; setTimeout(() => { try { d.remove(); } catch (e) {} }, 400); } catch (e) {} }, dur);- } catch (e) {}- }, text, ms);- } catch (e) {}-} // v1.9.7: reusable OS FOREGROUND raise, extracted verbatim from the proven browser_raise_os_window // path, so the wiki view-toggle callback can actually POP the relaunched window to the user's // screen. A jump-list click is a genuine USER action, so a real SetForegroundWindow raise is@@ -4803,10 +4801,9 @@ const server = http.createServer(async (req, res) => { const _switchMsg = view === 'authed' ? '\u{1F513} Switching to the LOGGED-IN view of the Adom wiki…' : '\u{1F4D6} Switching to the PUBLIC (logged-out) view of the Adom wiki…';+ // v1.9.11: OS caption (AD >=1.9.144). Fire-and-forget: the old window is torn down+ // moments later, so an OS-level surface is the ONLY thing that survives the switch. wikiCaption(_switchMsg, 30000).catch(() => {});- // v1.9.10: ALSO toast in the page itself (desktop_caption is relay-only pre-AD-fix) so- // a user watching the window sees the click registered before the teardown.- try { await wikiToast(session.page, _switchMsg, 8000); } catch (e) {} // Close the current window (mirror browser_close_window) so we can relaunch under the // other cookie jar. const oldProfile = session.profileName;@@ -4870,12 +4867,10 @@ const server = http.createServer(async (req, res) => { const _doneMsg = a && a.authed ? `\u{1F513} Adom wiki: now the LOGGED-IN view${a.user ? ` (${a.user})` : ''}` : '\u{1F513} Adom wiki: logged-in view needs the one-time sign-in — sign in in this window';- wikiCaption(_doneMsg, 4000).catch(() => {});- try { await wikiToast(s2.page, _doneMsg, 7000); } catch (e) {}+ wikiCaption(_doneMsg, 6000).catch(() => {}); } else { const _doneMsg = '\u{1F4D6} Adom wiki: now the PUBLIC (logged-out) view — what the world sees';- wikiCaption(_doneMsg, 4000).catch(() => {});- try { await wikiToast(s2.page, _doneMsg, 7000); } catch (e) {}+ wikiCaption(_doneMsg, 6000).catch(() => {}); } })().catch(() => {}); return;