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+1−1@@ -1,6 +1,6 @@ { "slug": "pup-bridge",- "version": "2.0.334",+ "version": "2.0.335", "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.334",+ "version": "2.0.335", "tags": [ "skills", "pup",
tools/pup-dashboard+8−1@@ -320,7 +320,14 @@ body{margin:0;background:#0d1117;color:var(--text);font:14px/1.5 var(--sans)} .ibtn:hover{color:var(--teal);border-color:var(--line);background:rgba(0,184,177,.08)} .ibtn:focus-visible{outline:2px solid var(--teal);outline-offset:1px} /* ── page body ── */-.wrap{max-width:1180px;margin:0 auto;padding:20px 20px 60px}+.wrap{margin:0 auto;padding:20px 20px 60px}+/* NO MAX-WIDTH on the layout (adom-ui-design 1.17.0, John saw the dead band on the right when he+ maximised the browser: "its like they hard coded their max width"). A dashboard is an APP+ SURFACE, not an article: it fills whatever it is given, a 700px webview pane or a 2500px+ maximised window, and extra width becomes more room for the prompts. The reading measure that+ prose genuinely needs is capped on the PARAGRAPH instead (.expl max-width:70ch), which is the+ one place a measure belongs. The only other caps left in this sheet are .led-detail's popover+ box and the two breakpoint media queries, neither of which constrains the page. */ /* item 6 (John, 2026-08-24: the collapsed gap did not match the open one). The CONTENT REGION owns the page padding, NOT the newbie panel. Before, .wrap had 0 top padding and the panel's own margin-top:16px supplied the gap under the header -- so the closed rule display:none