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.670",+ "version": "2.0.671", "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": "Every profile's lane survives a restart in its own jar: pup restores each profile's lane browser at boot (validated by the folder its processes run), adopts an unknown lane browser only into the profile it reports, and relaunches any window it finds inside another profile's browser. Before, after an upgrade the first unknown browser became the adom-you lane, so adom-you windows ran with another profile's cookies (AdomLapper, 2026-09-21)."+ "changelog": "Every profile's lane survives a restart in its own jar: pup restores each profile's lane browser at boot (validated by the folder its processes run), adopts an unknown lane browser only into the profile it reports and only after that restore, re-adopts each window on its own profile's lane, and relaunches any window it finds inside another profile's browser. Before, the first unknown browser after an upgrade became the adom-you lane, so adom-you windows ran with another profile's cookies, and windows on a second profile were never re-adopted (AdomLapper and CRR, 2026-09-21)." }
page.json+2−2@@ -4,7 +4,7 @@ "slug": "pup-bridge", "title": "Pup - Puppeteer Bridge", "brief": "pup is the AI's own browser: a real, full Chrome on the user's desktop that the AI fully controls (a sandbox, not the user's signed-in browser). Rides Bridge; pup_* verbs open windows and tabs, navigate, screenshot, and eval JS.",- "version": "2.0.670",+ "version": "2.0.671", "tags": [ "skills", "pup",@@ -168,5 +168,5 @@ "pup-bridge verbs are invoked through the adom-bridge CLI, not through a binary this package installs, so prefix rules cannot reach them." ] },- "changelog": "Every profile's lane survives a restart in its own jar: pup restores each profile's lane browser at boot (validated by the folder its processes run), adopts an unknown lane browser only into the profile it reports, and relaunches any window it finds inside another profile's browser. Before, after an upgrade the first unknown browser became the adom-you lane, so adom-you windows ran with another profile's cookies (AdomLapper, 2026-09-21)."+ "changelog": "Every profile's lane survives a restart in its own jar: pup restores each profile's lane browser at boot (validated by the folder its processes run), adopts an unknown lane browser only into the profile it reports and only after that restore, re-adopts each window on its own profile's lane, and relaunches any window it finds inside another profile's browser. Before, the first unknown browser after an upgrade became the adom-you lane, so adom-you windows ran with another profile's cookies, and windows on a second profile were never re-adopted (AdomLapper and CRR, 2026-09-21)." }