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
Dev skill: wedged-bridge diagnosis recipe (1.9.77 EISDIR spawn regression) + three-copy docs lesson; sync repo docs
2 files changed
+12−1
package.json+1−1@@ -1,6 +1,6 @@ { "slug": "adom-desktop-puppeteer-bridge",- "version": "1.8.9",+ "version": "1.8.10", "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-dev/SKILL.md+11@@ -166,6 +166,17 @@ What we learned and baked into the code: `browser_readiness`. If the runtime is ready and the bridge is running but verbs fail, it's an AD gate/ provisioning bug — report it with that evidence; it is not a pup code bug. +- **Wedged-bridge diagnosis recipe (learned on AD 1.9.77).** Symptoms: every `browser_*` verb times out+ but `ping`/core verbs work. Check `bridge_list` → `status:"running"` with `livePids:[]` = a bridge that+ crashed at spawn while AD still forwards to its dead port. Read `~/.adom/bridge-logs/puppeteer.log` —+ the 1.9.77 regression showed Node dying at boot: `EISDIR: lstat 'C:'` (AD mangled the entrypoint path at+ the drive-letter colon). Cross-check another box on a different AD version to isolate AD-vs-pup. pup+ can't fix AD's spawner — report with the log + version comparison (that report got it fixed same-day).+- **Docs can have THREE copies (SDK lesson, 2026-07-04).** The bridge-SDK page carried the same content in+ README.md, SKILL.md, AND bridges-SDK.md — an edit landed on two and left the third stale, so audits+ reading the third saw pre-update text. When auditing against a doc, verify the EXACT file you read; when+ publishing multi-copy docs, push and verify every copy.+ ## Publishing (the wiki has TWO storage layers — don't mix them) Full recipe in `PUBLISHING.md`. The load-bearing rules: