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.519",+ "version": "2.0.520", "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": [@@ -147,5 +147,5 @@ "prompt": "Download the puppeteer-bridge zip from the wiki and walk me through server.js" } ],- "changelog": "Re-assert the lane window's size and normal state on every open. fit ran only when dress_window first dressed a window, so a window that later ended up minimized was never corrected: pup reported the lane up and John had nothing on his screen, three times now. Chrome's own saved placement was already the full work area, so this is purely the window being minimized at the OS level afterwards. chrome.windows.update with state normal also restores a minimized window, and it does it without raising anything, which is why this goes through the extension rather than ab geometry."+ "changelog": "The extension lane keeps the taskbar contract the CDP lane keeps. John: 'why are you causing flashing of the windows taskbar icon when we've been through this 100 times ... you're supposed to default to showing progress bars in the icon. and why do i not see the overlay icon'. The lane made none of the three ab calls the CDP lane makes. Now: an indeterminate progress bar on the lane's button while open/navigate/tab run, cleared after (honouring taskbarActivity and minimalTouch exactly as activity.rs does); the active tab's favicon painted as the overlay badge, fetched by the extension itself since this lane has no CDP to fetch it with; and clear_attention after each of those, which removes the tint Windows paints when it denies Chrome the foreground. That tint was the flash: pup never called desktop_flash_window for this lane, the OS did it." }
page.json+2−2@@ -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.519",+ "version": "2.0.520", "tags": [ "skills", "pup",@@ -167,5 +167,5 @@ "pup-bridge verbs are invoked through the adom-bridge CLI, not through a binary this package installs, so prefix rules cannot reach them." ] },- "changelog": "Re-assert the lane window's size and normal state on every open. fit ran only when dress_window first dressed a window, so a window that later ended up minimized was never corrected: pup reported the lane up and John had nothing on his screen, three times now. Chrome's own saved placement was already the full work area, so this is purely the window being minimized at the OS level afterwards. chrome.windows.update with state normal also restores a minimized window, and it does it without raising anything, which is why this goes through the extension rather than ab geometry."+ "changelog": "The extension lane keeps the taskbar contract the CDP lane keeps. John: 'why are you causing flashing of the windows taskbar icon when we've been through this 100 times ... you're supposed to default to showing progress bars in the icon. and why do i not see the overlay icon'. The lane made none of the three ab calls the CDP lane makes. Now: an indeterminate progress bar on the lane's button while open/navigate/tab run, cleared after (honouring taskbarActivity and minimalTouch exactly as activity.rs does); the active tab's favicon painted as the overlay badge, fetched by the extension itself since this lane has no CDP to fetch it with; and clear_attention after each of those, which removes the tint Windows paints when it denies Chrome the foreground. That tint was the flash: pup never called desktop_flash_window for this lane, the OS did it." }