Pup - the AI's own browser

@@ -1,6 +1,6 @@ {   "slug": "pup-bridge",-  "version": "2.0.736",+  "version": "2.0.737",   "type": "app",   "description": "The pup SKILL PACK: the AI skills that teach a cloud/container AI how to drive the Bridge Puppeteer (pup) bridge (pup_* 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 Bridge 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 Bridge manages for you.",   "keywords": [@@ -187,5 +187,5 @@       "prompt": "Download the puppeteer-bridge zip from the wiki and walk me through server.js"     }   ],-  "changelog": "The site-session import (pup_import_browser_logins {sessionFor}) explains a 'no session' answer: how many cookies came back per browser profile, the decrypt stats, near matches and the field names (never a value), so a signed-in site that does not come over can be traced (John's laptop, 2026-10-28). Includes 2.0.735."+  "changelog": "WebRTC streaming apps work in pup again (pup-bridge#137): pup no longer launches its browser with --force-webrtc-ip-handling-policy=disable_non_proxied_udp and now writes Chrome's default WebRTC routing back into the profile, repairing existing profiles. The restriction never stopped the Windows Firewall prompt (#91; Adom Bridge's firewall rule handles that) and it left WebRTC media apps such as Google's Project Genie with no UDP candidates, so their calls never connected. Also: the site-session import reads Adom Bridge's source_browser / source_profile / http_only cookie fields, and its 'no session' answer explains what came back (from 2.0.736). Includes 2.0.735." }

@@ -4,7 +4,7 @@   "slug": "pup-bridge",   "title": "Pup - the AI's own browser",   "brief": "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.",-  "version": "2.0.736",+  "version": "2.0.737",   "tags": [     "skills",     "pup",@@ -207,5 +207,5 @@     "Kyle Bergstedt <[email protected]>",     "Colby Knox"   ],-  "changelog": "The site-session import (pup_import_browser_logins {sessionFor}) explains a 'no session' answer: how many cookies came back per browser profile, the decrypt stats, near matches and the field names (never a value), so a signed-in site that does not come over can be traced (John's laptop, 2026-10-28). Includes 2.0.735."+  "changelog": "WebRTC streaming apps work in pup again (pup-bridge#137): pup no longer launches its browser with --force-webrtc-ip-handling-policy=disable_non_proxied_udp and now writes Chrome's default WebRTC routing back into the profile, repairing existing profiles. The restriction never stopped the Windows Firewall prompt (#91; Adom Bridge's firewall rule handles that) and it left WebRTC media apps such as Google's Project Genie with no UDP candidates, so their calls never connected. Also: the site-session import reads Adom Bridge's source_browser / source_profile / http_only cookie fields, and its 'no session' answer explains what came back (from 2.0.736). Includes 2.0.735." }\ No newline at end of file