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
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.377",+ "version": "2.0.378", "tags": [ "skills", "pup",
skills/pup-browsers-and-chrome/SKILL.md+9@@ -121,3 +121,12 @@ almost never need (prefer typed verbs). If one returns `needs_approval` / `human run `adom-bridge-cli --target <box> request_shell_approval` (re-surfaces the dialog), ask the user to click Approve/Bypass, then **retry your original verb**. Never call `shell_auto_approve` (human-only, refuses). This is AD's own gate, NOT a Windows UAC.++## Temporary pins and the toolbar (v2.0.378)++- `pup_use {browser:"chrome"|"edge", temporary:true}` pins for a comparison or spike and **expires at+ the next bridge boot** (back to auto), so a forgotten pin can never strip the toolbar from every+ later launch. Pinning off CfT while the toolbar is on also returns a WARNING at pin time.+- Any `pup_open_window` whose window launched on a browser that cannot carry the Adom toolbar+ (branded Chrome ≥137, Edge) returns `_toolbarNotice` saying so; CfT is the only toolbar-capable+ engine and the default policy converges onto it.