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
SKILL.md+9@@ -50,6 +50,15 @@ Keep this model in mind and every verb makes sense: it's a pup-managed, persiste (the machine's own Chrome/Edge binary, a profile pup owns) driven by CDP — durable and shared by default, isolated only when you ask. +## Standing rule: TOAST THE USER before foregrounding (John, repeatedly)++NEVER put a window on the user's screen silently. Any time you FOREGROUND a pup window — a demo, a+"show me", a reveal, a real-cursor click that needs the window up — send an AD toast FIRST (or let+pup's auto-toast do it, v1.9.166+) so the user's attention is drawn to what just appeared. A window+that pops up with no heads-up reads as the agent hijacking the screen. pup now auto-fires+`notify_user` on every granted foreground, but you should still narrate WHY in the reason. For a+background nudge (not a full foreground), use `browser_alert_window` (taskbar flash) instead.+ ## When pup — vs the Adom extension (`nbrowser_*`) | The task | Tool |
package.json+1−1@@ -1,6 +1,6 @@ { "slug": "adom-desktop-puppeteer-bridge",- "version": "1.9.165",+ "version": "1.9.166", "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. So the pkg version (skills, bumps often) and the Release version (runtime, bumps rarely) differ on purpose. 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": "adom-desktop-puppeteer-bridge", "title": "Adom Desktop - Puppeteer Bridge", "brief": "The Adom Desktop Puppeteer (pup) bridge — drive a real headful browser on the user's desktop from the cloud: open/screenshot/eval/record. Cold-start drives the browser ALREADY on the machine (installed Chrome, else Microsoft Edge — every Windows PC ships with Edge) with a fresh isolated profile, so the common case needs NO download; Chrome for Testing is fetched only as a last resort. Two artifacts: the Releases zip is the bridge runtime (also bundled in Adom Desktop); the pkg installs the container-side Claude skills.",- "version": "1.9.165",+ "version": "1.9.166", "tags": [ "skills", "pup",