Pup - the AI's own browser

@@ -1,6 +1,6 @@ {   "slug": "pup-bridge",-  "version": "2.0.734",+  "version": "2.0.735",   "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": "pup keeps its own browser on the current Chrome Stable, silently (John, 2026-10-25: 'New Chrome available' showed in a pup window; pup had pinned one Chrome for Testing build, which has no updater, and it had fallen four major versions behind). A few minutes after start and every 6 hours pup checks Google's Chrome for Testing Stable channel and downloads a newer build in the background; the next browser start uses it. If pup's browser is still on the old build, pup restarts it once when no AI has used pup for 10 minutes and the user is not looking at a pup window; every window comes back at its page. The cache pruner now keeps the newest build instead of the pinned one, and readiness counts a newer build as ready. Setting browserAutoUpdate (on by default). Includes 2.0.733."+  "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." }

@@ -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.734",+  "version": "2.0.735",   "tags": [     "skills",     "pup",@@ -207,5 +207,5 @@     "Kyle Bergstedt <[email protected]>",     "Colby Knox"   ],-  "changelog": "pup keeps its own browser on the current Chrome Stable, silently (John, 2026-10-25: 'New Chrome available' showed in a pup window; pup had pinned one Chrome for Testing build, which has no updater, and it had fallen four major versions behind). A few minutes after start and every 6 hours pup checks Google's Chrome for Testing Stable channel and downloads a newer build in the background; the next browser start uses it. If pup's browser is still on the old build, pup restarts it once when no AI has used pup for 10 minutes and the user is not looking at a pup window; every window comes back at its page. The cache pruner now keeps the newest build instead of the pinned one, and readiness counts a newer build as ready. Setting browserAutoUpdate (on by default). Includes 2.0.733."+  "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." }\ No newline at end of file

@@ -49,6 +49,21 @@ After it finishes, reload the sign-in page (`pup_reload {}`). pup fills it in th `_autoLogin`. Confirm the live domain is the site you meant, then `pup_login {submit:true, submitReason:"<why this domain is right>"}` to sign in. +## When a site refuses pup's sign-in: bring the session over++Some sites refuse a fresh sign-in from pup's browser even with the right password or Google account. X (x.com) does,+answering "An unexpected error occurred". If the user is already signed in to that site in their own Chrome or Edge,+bring that session into pup instead of signing in:++```bash+adom-bridge --ai-thread "<your thread>" pup_import_browser_logins '{"sessionFor":"x.com","reason":"Bring your X session into pup so I can use X for you"}'+```++It uses the same approvals as the password import. It brings over only that site's cookies, sets them in pup's+browser, and never prints them. If several profiles are signed in, the answer is `several_sessions` with the list;+ask the user which account they mean, then pass `sourceProfile`. Per-site details are in `login-recipes/<domain>.md`+on the pup-bridge wiki page.+ ## On a Mac  The import is Windows-only today: it decrypts Chrome's saved passwords the Windows way. On a Mac,