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+1−1@@ -1,6 +1,6 @@ { "slug": "pup-bridge",- "version": "2.0.398",+ "version": "2.0.399", "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": [
page.json+1−1@@ -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.397",+ "version": "2.0.399", "tags": [ "skills", "pup",
skills/pup-progress/SKILL.md+2−1@@ -75,7 +75,8 @@ pup reports its own slow work in the SDK's measured-progress shape, so a bar can start kind), `confidence` (`measured` once 3+ samples exist, else `estimated`) and `startKind`. - **Live rows**: `pup_readiness` (the fast status verb, `statusVerb` everywhere) returns `active[]`, one row per in-flight phase: opens in flight, the Chrome-for-Testing download (percent + ETA from- the real byte rate), a consent toast waiting on the user (`blockedBy`), or a browser dialog+ the real byte rate), then a distinct `phase: "unpack"` row while the archive is unpacked in a+ supervised child process (v2.0.398; `unpackBytes`, `unpackMethod`), a consent toast waiting on the user (`blockedBy`), or a browser dialog (`blockedBy`). Empty `active[]` means idle. Poll it once a second while a slow verb runs. - **Blocked on a human is a RESPONSE, never a timeout** (v2.0.397, ab BRIDGE_SDK 2.1.30 hard rule): any pup verb parked on a human answers `{success:false, errorCode:"blocked_on_user", stillRunning,