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.712",+ "version": "2.0.713", "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": "pup says when a page load lands on a bot wall: Cloudflare (Just a moment / Verify you are human), PerimeterX (press and hold), Akamai (Access Denied), DataDome and generic bot checks come back as botWall with what to do instead (stop loading that site, use adom-parts-search for parts data, or ask the user for one click), not as a normal load. Loading pages from DigiKey, Mouser, Arrow, TI, Analog Devices, ST, Octopart or Newark within 15 s of the last one adds a pacing warning before the wall goes up (John's ECAS window, 2026-10-11). Includes 2.0.711."+ "changelog": "No more owner chip in the lower-left corner of pup pages: it covered the page's own controls there (a video player's buttons, a chat box), and the taskbar tile already names the thread. Off by default now; ownerChip:on in Settings brings it back (John, 2026-10-12). Includes 2.0.712: bot-wall detection and the pacing warning." }
page.json+2−2@@ -4,7 +4,7 @@ "slug": "pup-bridge", "title": "Pup - the AI's own browser", "brief": "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.",- "version": "2.0.712",+ "version": "2.0.713", "tags": [ "skills", "pup",@@ -168,5 +168,5 @@ "Kyle Bergstedt <[email protected]>", "Colby Knox" ],- "changelog": "pup says when a page load lands on a bot wall: Cloudflare (Just a moment / Verify you are human), PerimeterX (press and hold), Akamai (Access Denied), DataDome and generic bot checks come back as botWall with what to do instead (stop loading that site, use adom-parts-search for parts data, or ask the user for one click), not as a normal load. Loading pages from DigiKey, Mouser, Arrow, TI, Analog Devices, ST, Octopart or Newark within 15 s of the last one adds a pacing warning before the wall goes up (John's ECAS window, 2026-10-11). Includes 2.0.711."+ "changelog": "No more owner chip in the lower-left corner of pup pages: it covered the page's own controls there (a video player's buttons, a chat box), and the taskbar tile already names the thread. Off by default now; ownerChip:on in Settings brings it back (John, 2026-10-12). Includes 2.0.712: bot-wall detection and the pacing warning." }
skills/pup-settings/SKILL.md+1−1@@ -117,7 +117,7 @@ flows live in `login-recipes/` on the wiki page. | Key | Default | What it does | |---|---|---|-| `ownerChip` | **on** | A tiny non-interactive chip, bottom-left, naming the owning AI thread + profile. Click-through, can't disturb the page. |+| `ownerChip` | **off** (since 2.0.713) | A tiny chip, bottom-left, naming the owning AI thread + profile. Off by default: it covers whatever the page puts in that corner (a video player's controls, a chat box), and the taskbar tile already names the thread. | | `titleTag` | **off** | Append "(ai-thread: <name>)" to the window title. Off, many pages manage their own title. | | `titlePrefix` | **off** | Prepend the owning thread (+ wiki signed-in/out) to the title. Off, pup does not mangle page titles by default (see the page-integrity doctrine). |