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 with its AI thread's name in your taskbar or dock.
← Commit history
Publish skill: document the AD 1.9.79 per-verb timeouts contract + pup's declared budgets
2 files changed
+10−1
package.json+1−1@@ -1,6 +1,6 @@ { "slug": "adom-desktop-puppeteer-bridge",- "version": "1.8.10",+ "version": "1.8.11", "type": "app", "description": "CONTAINER-SIDE install \u2014 the pup skill pack in the wiki skillpack layout: the everyday `pup` user skill PLUS two bundled developer sub-skills (pup-bridge-dev, pup-bridge-publish; user-invocable:false, DEVELOPER-only descriptions so they never trigger for everyday users), all dropped into ~/.claude/skills/ AND ~/.codex/skills/ by an explicit install.sh list. It does NOT contain the bridge runtime: the bridge (Node + browser driving) lives on the DESKTOP \u2014 bundled inside Adom Desktop and published on the Releases tab as adom-bridge-puppeteer-v<ver>.zip, which Adom Desktop streams into its bridges-cache. TL;DR: pkg install = the skill pack; the bridge = the Release zip + bundled in Adom Desktop.", "keywords": [
skills/pup-bridge-publish/SKILL.md+9@@ -234,3 +234,12 @@ no manual kill, no bridge_install force needed for the update path. Then PROVE i the running process's /status version — keep BRIDGE_VERSION correct). If a process serves stale code, `restart_bridge '{"name":"puppeteer"}'` kills (tracked PIDs + port orphans) and respawns from cache. Drop any taskkill/manual-PID habits.++## Per-verb timeout budgets (AD >= 1.9.79 contract)++bridge.json declares `timeouts` with BARE verb keys (no browser_ prefix): resolution = exact `verbs` ->+first matching `prefixes` -> `default` -> AD global 60s. pup declares: prewarm 240 (blocking CfT download),+use 240 (browser_use can trigger installs), open_window 150 (spawn-verified fallback worst case = 3+candidates x 3 attempts x 30s CDP wait), record* 90. An AD timeout is NON-terminal: callers get+{stillRunning:true, statusVerb, timeoutSeconds} and poll browser_readiness. When adding a verb that can+block >60s, add its bare key here AND bump runtime version (bridge.json+BRIDGE_VERSION+manifest+zip).