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
Publish 2.0.304
3 files changed
+7−4
package.json+1−1@@ -1,6 +1,6 @@ { "slug": "pup-bridge",- "version": "2.0.303",+ "version": "2.0.304", "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.303",+ "version": "2.0.304", "tags": [ "skills", "pup",
skills/pup-taskbar-progress/SKILL.md+5−2@@ -45,8 +45,11 @@ Any other operation can get one (see the dev note). Notes: - **Windows only.** macOS/Linux have no taskbar, so the setting is stored but inert.-- A STOP of a leftover flash, and a human explicitly clicking "flash" in the dashboard, still work- regardless of the setting — only pup's own *automatic* flashes are gated off in `progress`/`off`.+- In `progress` mode pup NEVER paints orange, not even for an explicit `pup_alert_window`: the+ nudge becomes a 2.5s full progress pulse on the button (v2.0.304). A STOP of a leftover flash+ still works. If you ever see an orange flash in `progress` mode, it is Windows itself: the shell+ flashes a button when a background process is denied the foreground, which Chrome can trigger on+ its own; pup did not ask for it. - **This is now the ONE taskbar-activity control.** As of v2.0.292 it absorbed the former separate `openFlash` (flash on open), `autoFlash` (flash on a mutating verb), and `agentActivity` ("an AI is driving this" strip) toggles — they are gone. `taskbarActivity: flash` gives the old open+mutate