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
SDK re-audit: pup is open source, so ship dev/publish skills in skills/<name>/ scoped user-invocable:false (dev-skills/*.md is dead per the Bridge SDK checklist); skillpack package.json dependencies emptied to {}; docs corrected
1 file changed
+5−4
CLAUDE.md+5−4@@ -16,7 +16,7 @@ via the `updateManifestUrl` in `bridge.json`. (Extracted from `adom-desktop/plug dir on spawn (this bridge ships source-only; node_modules is reconstructed there + present in the seed). - **YOU (this bridge) own:** every `browser_*` / `desktop_record_*` verb + its response `_hint`s, the **Chrome-for-Testing self-heal** (`src/chrome.js` — detect / auto-install / readiness), the status-chip- fields on `/status`, the `browser_describe` catalog, the `pup` `SKILL.md` (+ maintainer skills in `dev-skills/`/`publish-skills/`), and the edit →+ fields on `/status`, the `browser_describe` catalog, the `pup` `SKILL.md` (+ the shipped maintainer skills `skills/pup-bridge-{dev,publish}`), and the edit → publish → reinstall loop. - So: a `browser_*` verb misbehaves, a hint is missing, Chrome-for-Testing won't install, the chip lies → it's **your code**, fix it here and republish. It is NOT an adom-desktop request. If a GENERIC AD@@ -37,9 +37,10 @@ via the `updateManifestUrl` in `bridge.json`. (Extracted from `adom-desktop/plug - `src/recorder.html` / `welcome.html` / icons — recorder UI + assets. - `adom-bridge-puppeteer-manifest.json` (repo root) — the streaming manifest AD's `updateManifestUrl` points at; its `url` is the RELEASE download URL of the zip, with matching `sha256`/`size`.-- `SKILL.md` (root) — the ONLY user skill (`pup`), installed into `~/.claude/skills/` (via `install.sh` /- `adom-wiki pkg`). The cold-start playbook lives here. The maintainer skills live in `dev-skills/` +- `publish-skills/` — auto-excluded from the pkg tarball, so they NEVER ship to a user's container.+- `SKILL.md` (root) — the user skill (`pup`), installed into `~/.claude/skills/` (via `install.sh` /+ `adom-wiki pkg`). The cold-start playbook lives here. The maintainer skills (`skills/pup-bridge-dev`,+ `skills/pup-bridge-publish`) DO ship in the pkg scoped `user-invocable:false` — per the Bridge SDK,+ an OPEN-SOURCE bridge ships its dev/publish skills; a closed one keeps them private. (`dev-skills/*.md` is dead.) ## The publish/reinstall loop