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.533",+ "version": "2.0.534", "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": [@@ -147,5 +147,5 @@ "prompt": "Download the puppeteer-bridge zip from the wiki and walk me through server.js" } ],- "changelog": "An extension-lane session is re-adopted across a pup restart, never relaunched, while its Chrome window is still in the lane browser. Recovery's liveness check is CDP-based, which an ext window never satisfies, so a restart declared both ext sessions' Chrome gone and relaunched them as new windows beside the originals (the 17-tab proof window orphaned, a duplicate opened next to it). The session file carries windowId; the live tabs listing says whether that window still exists and which tabs it holds, and the session is rebuilt from that, at boot and on the health tick."+ "changelog": "The identity button shows the user's avatar. Chrome lets an extension set its action icon at any time (chrome.action.setIcon with imageData), so the identity extension now has a service worker that fetches the adom-you avatar through a new pup endpoint, GET /identity/avatar (pup fetches it server-side with its own token, cached 10 min, so the extension needs no host permission for wherever the avatar lives), draws it circle-cropped onto the family's teal tile at 16/32/48/128, and sets it as the button; refreshed every 10 minutes and retried every 30 s until pup answers. John: 'you should be showing my avatar up in your button in the chrome toolbar ... or can you just do it dynamically whenever you want?' Yes, dynamically." }
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.533",+ "version": "2.0.534", "tags": [ "skills", "pup",@@ -167,5 +167,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": "An extension-lane session is re-adopted across a pup restart, never relaunched, while its Chrome window is still in the lane browser. Recovery's liveness check is CDP-based, which an ext window never satisfies, so a restart declared both ext sessions' Chrome gone and relaunched them as new windows beside the originals (the 17-tab proof window orphaned, a duplicate opened next to it). The session file carries windowId; the live tabs listing says whether that window still exists and which tabs it holds, and the session is rebuilt from that, at boot and on the health tick."+ "changelog": "The identity button shows the user's avatar. Chrome lets an extension set its action icon at any time (chrome.action.setIcon with imageData), so the identity extension now has a service worker that fetches the adom-you avatar through a new pup endpoint, GET /identity/avatar (pup fetches it server-side with its own token, cached 10 min, so the extension needs no host permission for wherever the avatar lives), draws it circle-cropped onto the family's teal tile at 16/32/48/128, and sets it as the button; refreshed every 10 minutes and retried every 30 s until pup answers. John: 'you should be showing my avatar up in your button in the chrome toolbar ... or can you just do it dynamically whenever you want?' Yes, dynamically." }