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
package.json+2−2@@ -1,6 +1,6 @@ { "slug": "pup-bridge",- "version": "2.0.729",+ "version": "2.0.730", "type": "app", "description": "The pup SKILL PACK: the AI skills that teach a cloud/container AI how to drive the Bridge Puppeteer (pup) bridge (pup_* 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 Bridge 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 Bridge manages for you.", "keywords": [@@ -148,5 +148,5 @@ "prompt": "Download the puppeteer-bridge zip from the wiki and walk me through server.js" } ],- "changelog": "pup notices when its browser has lost 3D graphics and fixes it. After its GPU process crashes a few times, Chrome stops using the GPU for the rest of that browser session and current Chrome has no software fallback, so every WebGL page (the wiki's 3D viewer) failed in pup with 'Cannot read properties of null (reading alpha)' (John, 2026-10-20). pup now tests WebGL in one of its windows every 5 minutes; after two failed tests in a row it restarts its browser at a quiet moment (no AI using a pup window for a minute, at most every 30 minutes), checks 3 minutes later that every saved window came back and restarts once more if not (pup-bridge#134), and the user gets a toast saying why. Includes 2.0.727."+ "changelog": "pup_eval and pup_login work on strict pages again (pup-bridge#130): American Express's login page refuses page scripts with 'eval is disabled', a wording pup's fallback did not recognize, so both failed on the extension lane; they now fall back to the DevTools path as on other strict pages. macOS (Kyle's pull request #5): --use-mock-keychain on every Chrome launch so a new browser build never pops a keychain prompt, a depth-counted capture guard, and tools/rust-build-macos.sh. No change on Windows from the macOS parts. Includes 2.0.729." }
page.json+2−2@@ -4,7 +4,7 @@ "slug": "pup-bridge", "title": "Pup - the AI's own browser", "brief": "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.",- "version": "2.0.729",+ "version": "2.0.730", "tags": [ "skills", "pup",@@ -168,5 +168,5 @@ "Kyle Bergstedt <[email protected]>", "Colby Knox" ],- "changelog": "pup notices when its browser has lost 3D graphics and fixes it. After its GPU process crashes a few times, Chrome stops using the GPU for the rest of that browser session and current Chrome has no software fallback, so every WebGL page (the wiki's 3D viewer) failed in pup with 'Cannot read properties of null (reading alpha)' (John, 2026-10-20). pup now tests WebGL in one of its windows every 5 minutes; after two failed tests in a row it restarts its browser at a quiet moment (no AI using a pup window for a minute, at most every 30 minutes), checks 3 minutes later that every saved window came back and restarts once more if not (pup-bridge#134), and the user gets a toast saying why. Includes 2.0.727."+ "changelog": "pup_eval and pup_login work on strict pages again (pup-bridge#130): American Express's login page refuses page scripts with 'eval is disabled', a wording pup's fallback did not recognize, so both failed on the extension lane; they now fall back to the DevTools path as on other strict pages. macOS (Kyle's pull request #5): --use-mock-keychain on every Chrome launch so a new browser build never pops a keychain prompt, a depth-counted capture guard, and tools/rust-build-macos.sh. No change on Windows from the macOS parts. Includes 2.0.729." }