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.376: Consent toasts now RETRACT on timeout: a reminder toast is sticky and ab never auto-dismisses it, while timeoutSec only bounds the verb's wait - so an expired Approve/Reveal offer used to stay on screen where a late click looked like an authorization pup had already stopped listening for. Both consent verbs (pup_fill_card, pup_credential_reveal) now call notify_dismiss the moment the wait expires, and the toast bodies state the 2-minute expiry.
5 files changed
+22−13
adom-bridge-puppeteer-manifest.json+5−5@@ -1,10 +1,10 @@ { "manifest_version": 1, "name": "puppeteer",- "version": "2.0.375",- "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.375/adom-bridge-puppeteer-v2.0.375.zip",- "sha256": "097fcb2f862b08c19981dcac032bdf62e54095bfd5a535f5fc970f941fb1bbe1",- "size": 1545553,+ "version": "2.0.376",+ "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.376/adom-bridge-puppeteer-v2.0.376.zip",+ "sha256": "e36166c97f4fad6daa9dbd0fb487402dd014a833797e3e8599d78d9c127a949b",+ "size": 1545866, "verbPrefixes": [ "browser_", "desktop_recorder_",@@ -12,5 +12,5 @@ ], "healthEndpoint": "/status", "statusVerb": "browser_readiness",- "released_at": "2026-09-02T15:40:06.671430Z"+ "released_at": "2026-09-02T15:43:23.837272Z" }
package.json+1−1@@ -1,6 +1,6 @@ { "slug": "pup-bridge",- "version": "2.0.375",+ "version": "2.0.376", "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.375+2.0.376
src/bridge.json+1−1@@ -2,7 +2,7 @@ "manifest_version": 1, "name": "puppeteer", "displayName": "Puppeteer (Chrome for Testing + Native)",- "version": "2.0.375",+ "version": "2.0.376", "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−5@@ -19493,7 +19493,7 @@ const server = http.createServer(async (req, res) => { const r = await chrome.abCommand('notify_user', { id: toastId, level: 'warning', scenario: 'reminder', title: `Reveal your ${host} login to ${who}?`,- body: `${who} is asking pup for the saved login for ${host} (username ${cred.username}). Reason given: "${reason}". Reveal sends the password to that caller ONCE. Deny sends nothing.`,+ body: `${who} is asking pup for the saved login for ${host} (username ${cred.username}). Reason given: "${reason}". Reveal sends the password to that caller ONCE. Deny sends nothing. This request expires in 2 minutes.`, buttons: [{ label: 'Reveal' }, { label: 'Deny' }], wait: true, timeoutSec: 120, }, { timeoutMs: 130000, callerThread: _callerThread || undefined, callerReason: reason });@@ -19502,7 +19502,12 @@ const server = http.createServer(async (req, res) => { } catch (e) { decision = null; } if (decision !== 'Reveal') { const code = decision ? 'consent_declined' : 'consent_timeout';- console.log(`[credential] reveal ${code.toUpperCase()} for ${host} by "${who}"`);+ // v2.0.376 (John): a reminder toast is STICKY — ab never auto-dismisses it, and+ // timeoutSec only bounds OUR wait. Without this retract, an expired consent toast+ // stays on screen and a late click looks like an authorization pup already stopped+ // listening for. On decline the user's own click dismissed it; on timeout WE must.+ if (!decision) { try { chrome.abCommand('notify_dismiss', { id: toastId }, { timeoutMs: 8000 }).catch(() => {}); } catch (e) {} }+ console.log(`[credential] reveal ${code.toUpperCase()} for ${host} by "${who}"${decision ? '' : ' — toast retracted'}`); sendJSON(res, { success: false, errorCode: code, error: code === 'consent_declined' ? 'the user declined on the desktop; nothing was revealed' : 'the user did not answer the consent toast within 120s; nothing was revealed', _hint: 'Do not retry in a loop. If the user wants this, they will click Reveal on the next ask.' }); return; }@@ -19559,11 +19564,12 @@ const server = http.createServer(async (req, res) => { // never reach the caller, and the human click is the authorization for this one fill. console.log(`[card] fill REQUESTED ${nickname} (…${meta.last4}) on ${merchant}${amount ? ' for ' + amount : ''} by "${who}" — asking the user`); let decision = null;+ const cardToastId = `cardfill-${Date.now().toString(36)}`; try { const r = await chrome.abCommand('notify_user', {- id: `cardfill-${Date.now().toString(36)}`, level: 'warning', scenario: 'reminder',+ id: cardToastId, level: 'warning', scenario: 'reminder', title: `Pay with ${meta.brand} …${meta.last4} on ${merchant}?`,- body: `${who} wants to fill your card "${nickname}" (${meta.brand} ending ${meta.last4}) into the checkout on ${merchant}${amount ? ` for ${amount}` : ''}. Approve fills the card fields in the pup window so you (or the AI) can submit. Deny fills nothing.`,+ body: `${who} wants to fill your card "${nickname}" (${meta.brand} ending ${meta.last4}) into the checkout on ${merchant}${amount ? ` for ${amount}` : ''}. Approve fills the card fields in the pup window so you (or the AI) can submit. Deny fills nothing. This request expires in 2 minutes.`, buttons: [{ label: 'Approve' }, { label: 'Deny' }], wait: true, timeoutSec: 120, }, { timeoutMs: 130000, callerThread: _callerThread || undefined, callerReason: `fill card ${nickname} on ${merchant}` });@@ -19572,7 +19578,10 @@ const server = http.createServer(async (req, res) => { } catch (e) { decision = null; } if (decision !== 'Approve') { const code = decision ? 'consent_declined' : 'consent_timeout';- console.log(`[card] fill ${code.toUpperCase()} ${nickname} on ${merchant} by "${who}"`);+ // v2.0.376: retract the sticky toast on timeout (see the credential_reveal note) —+ // an expired approval offer must not sit on screen looking clickable.+ if (!decision) { try { chrome.abCommand('notify_dismiss', { id: cardToastId }, { timeoutMs: 8000 }).catch(() => {}); } catch (e) {} }+ console.log(`[card] fill ${code.toUpperCase()} ${nickname} on ${merchant} by "${who}"${decision ? '' : ' — toast retracted'}`); sendJSON(res, { success: false, errorCode: code, error: code === 'consent_declined' ? 'the user declined the card fill on the desktop; nothing was filled' : 'the user did not answer the approval toast within 120s; nothing was filled', _hint: 'Do not retry in a loop. Tell the user what you were trying to buy and let them re-initiate.' }); return; }