Pup - the AI's own browser

@@ -1,6 +1,6 @@ {   "slug": "pup-bridge",-  "version": "2.0.735",+  "version": "2.0.736",   "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": "x.com and other sites that refuse a fresh sign-in from pup's browser (John, 2026-10-27, pup-bridge#136): pup_import_browser_logins {sessionFor:'x.com'} brings the user's existing signed-in session for one site over from their own Chrome or Edge (the same Adom Bridge consent and Windows prompt as the password import), sets its cookies in pup's browser, and never prints them. A popup a pup click opens (an OAuth or Sign in with Google window) is adopted in the background within about 2 s instead of 30 to 40 s, and the click's answer says where it will appear, so an AI drives it with pup verbs and never reaches for the real mouse. New login recipe login-recipes/x.com.md; the pup-import-logins skill covers the session import. Includes 2.0.734."+  "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." }

@@ -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.735",+  "version": "2.0.736",   "tags": [     "skills",     "pup",@@ -207,5 +207,5 @@     "Kyle Bergstedt <[email protected]>",     "Colby Knox"   ],-  "changelog": "x.com and other sites that refuse a fresh sign-in from pup's browser (John, 2026-10-27, pup-bridge#136): pup_import_browser_logins {sessionFor:'x.com'} brings the user's existing signed-in session for one site over from their own Chrome or Edge (the same Adom Bridge consent and Windows prompt as the password import), sets its cookies in pup's browser, and never prints them. A popup a pup click opens (an OAuth or Sign in with Google window) is adopted in the background within about 2 s instead of 30 to 40 s, and the click's answer says where it will appear, so an AI drives it with pup verbs and never reaches for the real mouse. New login recipe login-recipes/x.com.md; the pup-import-logins skill covers the session import. Includes 2.0.734."+  "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." }\ No newline at end of file