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+1−1@@ -1,7 +1,7 @@ --- name: pup user-invocable: true-description: "Drive a browser on the user's desktop from the cloud: the Puppeteer 'pup' bridge (pup_* verbs via the adom-bridge-cli CLI). To the user these are PUP WINDOWS, full stop: never name the browser build or how pup drives it unless they ask. pup runs its own browser in a pup-managed DURABLE profile (logins/localStorage persist and are shared across pup windows), driven through pup's own extension channel with no debug port, which is the lane every vendor site loads on and the ONLY lane pup opens unless you pass lane:'cdp' for a CDP-only feature (see the pup-lanes skill), in the BACKGROUND so it never disturbs the user; NOT the user's real signed-in profile (that is the Adom extension's nbrowser_* verbs), NOT headless (a real rendered window, so screenshots/recording are true-to-life). USE PUP INSTEAD OF HEADLESS CHROME: never launch puppeteer-core, Playwright or a headless Chromium in the container to screenshot, render or check a page (John, 2026-10-06): the container's software GPU renders WebGL slowly and crashes on 3D pages, while pup has the desktop's real GPU and reaches container servers through the Hydrogen proxy (http://<port>.localhost:<proxy port>/, from $VSCODE_PROXY_URI). Open/close windows + tabs, navigate, screenshot, eval JS, record. This is the START-HERE skill: the mental model + when-to-use + the skill map; deeper topics route to the sub-skills. For 'is it ready' use pup_readiness (not pup_status). Trigger words: pup, puppeteer, headless chrome, headless chromium, headless browser, puppeteer-core, playwright, screenshot a web page, screenshot my page, render a page, render the 3D view, check a page renders, webgl screenshot, browser window, open in pup, open my app in pup, browser screenshot, browser eval, browser reload, visual debug, headful chrome, pup_open_window, pup_screenshot, pup_readiness, pup_prewarm, chrome for testing, open in browser, open my web app, show my app in the browser, preview my app, open the app I just built, view my app, open localhost, show my dev server, pup_login, log into a site in pup, autofill password, saved login, durable profile, isolated window."+description: "Drive a browser on the user's desktop from the cloud: the Puppeteer 'pup' bridge (pup_* verbs via the adom-bridge-cli CLI). To the user these are PUP WINDOWS, full stop: never name the browser build or how pup drives it unless they ask. pup runs its own browser in a pup-managed DURABLE profile (logins/localStorage persist and are shared across pup windows), driven through pup's own extension channel with no debug port, which is the lane every vendor site loads on and the ONLY lane pup opens unless you pass lane:'cdp' for a CDP-only feature (see the pup-lanes skill), in the BACKGROUND so it never disturbs the user; NOT the user's real signed-in profile (that is the Adom extension's nbrowser_* verbs), NOT headless (a real rendered window, so screenshots/recording are true-to-life). Open/close windows + tabs, navigate, screenshot, eval JS, record. This is the START-HERE skill: the mental model + when-to-use + the skill map; deeper topics route to the sub-skills. For 'is it ready' use pup_readiness (not pup_status). Trigger words: pup, puppeteer, browser window, open in pup, open my app in pup, browser screenshot, browser eval, browser reload, visual debug, headful chrome, pup_open_window, pup_screenshot, pup_readiness, pup_prewarm, chrome for testing, open in browser, open my web app, show my app in the browser, preview my app, open the app I just built, view my app, open localhost, show my dev server, pup_login, log into a site in pup, autofill password, saved login, durable profile, isolated window." --- # Pup: browser control on the user's desktop (start here)
package.json+2−2@@ -1,6 +1,6 @@ { "slug": "pup-bridge",- "version": "2.0.701",+ "version": "2.0.702", "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": "Annotate starts in Multi mode: draw several shapes, press Enter to finish. Space toggles Multi and Single (the old Auto), M and S pick one, Esc cancels, and a hint under the toolbar shows the keys (John, 2026-10-06). Includes 2.0.700: the taskbar progress bar on every page load, restored videos kept paused, update notices."+ "changelog": "The toolbar pen works on pages that change their address in place (Slack, Gmail, YouTube): it finds its window by the browser's tab id, not by the page address pup last recorded, and falls back to the pup window in front. A pen click that still cannot start shows a ! on the button with the reason, and pup logs it (John's Slack window, 2026-10-07: 'it didn't ever show me the toolbar')." }
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.701",+ "version": "2.0.702", "tags": [ "skills", "pup",@@ -168,5 +168,5 @@ "Kyle Bergstedt <[email protected]>", "Colby Knox" ],- "changelog": "Annotate starts in Multi mode: draw several shapes, press Enter to finish. Space toggles Multi and Single (the old Auto), M and S pick one, Esc cancels, and a hint under the toolbar shows the keys (John, 2026-10-06). Includes 2.0.700: the taskbar progress bar on every page load, restored videos kept paused, update notices."+ "changelog": "The toolbar pen works on pages that change their address in place (Slack, Gmail, YouTube): it finds its window by the browser's tab id, not by the page address pup last recorded, and falls back to the pup window in front. A pen click that still cannot start shows a ! on the button with the reason, and pup logs it (John's Slack window, 2026-10-07: 'it didn't ever show me the toolbar')." }