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
README.md+10−5@@ -1,11 +1,16 @@ # Adom Desktop — Puppeteer (pup) Bridge Drive a browser on the user's desktop from the cloud: open/close windows + tabs, navigate, screenshot,-eval JS, record windows. pup is a **generic, non-profile browser** — every session is a **fresh, isolated-Chrome/Edge process**, never the user's real signed-in browser. It drives the browser **already on the-machine** (installed Chrome, else Microsoft Edge — every Windows PC ships Edge), so the common case needs-**no download**; **Chrome for Testing** is auto-fetched only as a last resort when the box has no-Chromium browser at all. Windows open in the **background by default** so pup never disrupts the user.+eval JS, record windows. pup drives the browser **already on the machine** (installed Chrome, else+Microsoft Edge; every Windows PC ships Edge), never the user's real signed-in browser, with windows+opening in the **background by default** so pup never disrupts the user.++**The core goal: an AI-driven browser that can do everything it needs to for you - the best assistant+in the world.** By default every pup window surfs on the shared durable **adom-you** profile, and every+login made there enriches a shared credential store. Over time that store lets pup automatically enter+usernames and passwords on every site it has ever seen, which is what makes a truly self-sufficient+AI browser possible. Isolated throwaway profiles exist for the cases that need them (logged-out+testing, acting as another user), but they build nothing: adom-you is the default on purpose. > To drive the user's **real, signed-in** Chrome/Edge (their cookies, SSO, saved logins), that's the > **Adom browser extension's `nbrowser_*` verbs** — a separate bridge, not pup.
SKILL.md+14@@ -14,6 +14,20 @@ adom-desktop --ai-thread "<your thread>" browser_open_window '{"sessionId":"myta adom-desktop --ai-thread "<your thread>" browser_screenshot '{"sessionId":"mytask-web"}' ``` +## THE CORE GOAL (John's words, so everyone truly understands it)++pup exists to be **an AI-driven browser that can do everything it needs to for you: the best+assistant in the world**. The engine of that goal is the shared durable **adom-you** profile:++- **Surf as adom-you by default.** Every pup window on adom-you contributes every login it makes to+ the shared credential store. The more windows surf as adom-you, the better the username/password+ database gets, and over time pup can automatically sign in to every website it has ever seen.+- **Isolation is the exception, not a style choice.** Pass `isolated:true` (or a separate profile)+ ONLY when the task genuinely needs a clean jar: testing logged-out views, acting as a different+ user, untrusted pages. An isolated window's logins are thrown away: they build nothing.+- The dashboard shows a "surfing as adom-you" chip per window and an adom-you count in the header:+ if your window says "NOT adom-you", have a reason.+ ## The mental model — what pup actually is (read this once) pup is a small **Node bridge** that Adom Desktop spawns on the user's machine. When you open a window it
package.json+1−1@@ -1,6 +1,6 @@ { "slug": "adom-desktop-puppeteer-bridge",- "version": "1.9.271",+ "version": "1.9.272", "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.271",+ "version": "1.9.272", "tags": [ "skills", "pup",