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
HANDOFF-TO-ADOM-DESKTOP.md+2−2@@ -15,7 +15,7 @@ exactly like the kicad and fusion bridges: - **Manifest (updateManifestUrl target):** `https://wiki.adom.inc/api/v1/pages/adom-desktop-puppeteer-bridge/files/adom-bridge-puppeteer-manifest.json` - **Release zip:** `https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.1.0/adom-bridge-puppeteer-v1.1.0.zip` (sha256 `525eabb0350ea0eaf52a949e9b3026f5a4a035868afe9546a7478298b9539b8c`, source-only — node_modules is reconstructed by AD's `npm install` on spawn, as today) -**What changed in 1.1.0 (the reason for all this):** cold-start self-heal. On a fresh PC (HD bundles+**What changed in 1.1.0 (the reason for all this):** cold-start self-heal. On a fresh PC (Hydrogen bundles AD; the installer pre-installs neither Node nor Chrome for Testing), the first "open in pup" used to fail with a generic "Failed to launch Chrome after 3 attempts" + a dev string (npx…). Now the bridge detects a missing Chrome for Testing, auto-installs it (programmatically via the bundled@@ -60,7 +60,7 @@ unchanged and still correct. - after AD enters embedded mode, fire `browser_prewarm` once (fire-and-forget) to kick the Chrome download in the background. Either way, gate it behind the existing Node check (if Node is missing it's a no-op / the- `node_not_found` path stays the recovery). Net effect: a fresh HD install quietly warms pup so the+ `node_not_found` path stays the recovery). Net effect: a fresh Hydrogen install quietly warms pup so the user's first "open in pup" is instant instead of a 2–3 min download. **Verify after your change:** on a fresh embedded boot with Node present, `bridge_list` shows pup at