← Commit history

Publish 2.0.490

John Lauer ·917d43eba1 ·1mo ago ·parent 3f8d502
3 files changed +37−4
SKILL.md+33
@@ -341,6 +341,39 @@ until they're back — it clicks NOTHING while they're not ready), then does the hover→click and narrates each step. This is the protocol so pup never foregrounds-and-acts while the user is not ready. ++## Walled by a vendor site? Extension-driven windows (no CDP debug port)++Some vendor edges do not wall *you*, they wall the **DevTools debug port**. Measured on one box in one+minute (pup-bridge#109): over CDP, st.com and mouser.com died with `ERR_HTTP2_PROTOCOL_ERROR` and+arrow.com answered `Access Denied`; driven through the pup extension with no debug port, all three load.+The extension-driven browser was the SAME Chrome for Testing binary reporting raw Chromium brands with no+"Google Chrome" brand at all, so the discriminator is the debug port, not your identity. Driving the real+installed Chrome binary over CDP failed identically, and matching the consumer UA and brands, hiding+`navigator.webdriver`, suppressing `Runtime.enable`, normalising permissions and feeding trusted CDP input+all changed nothing.++```bash+adom-bridge-cli --ai-thread "<thread>" pup_ext_open     '{"url":"https://www.arrow.com/"}'+adom-bridge-cli --ai-thread "<thread>" pup_ext_navigate '{"url":"https://www.mouser.com/"}'+adom-bridge-cli --ai-thread "<thread>" pup_ext_eval     '{"expr":"document.title"}'+adom-bridge-cli --ai-thread "<thread>" pup_ext_tabs     '{}'+adom-bridge-cli --ai-thread "<thread>" pup_ext_close    '{}'+```++**Give it time.** These windows load like a human's browser, not like a CDP driver you can await: settle+15s or so after open/navigate before you read, and re-read rather than declaring a page empty. A body of 0+chars WITH a title is a bot wall, not a slow load.++**What it cannot do.** No CDP means no focus emulation, no user-agent override, no precise trusted input,+no annotate overlay, no taskbar identity, and it is NOT part of the normal window/session model+(`pup_list_windows` does not show it). Use it for pages that wall CDP; use normal pup windows for+everything else.++**When it will NOT help.** A site that denies a profile with no established trust denies every client,+including the user's real Chrome driven by the real extension (analog.com does exactly this on a cold+profile). That is a human-visit problem, not a driver problem — surface it and let the human load it once.+ ## When pup — vs the Adom extension (`nbrowser_*`)  | The task | Tool |
package.json+2−2
@@ -1,6 +1,6 @@ {   "slug": "pup-bridge",-  "version": "2.0.489",+  "version": "2.0.490",   "type": "app",   "description": "The pup SKILL PACK \u2014 the AI skills that teach a cloud/container AI how to drive the Adom Desktop Puppeteer (pup) bridge (browser_* 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 Desktop 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 Desktop manages for you.",   "keywords": [@@ -147,5 +147,5 @@       "prompt": "Download the puppeteer-bridge zip from the wiki and walk me through server.js"     }   ],-  "changelog": "extension-driven mode: correct tab targeting, liveness and close (#109)"+  "changelog": "teach extension-driven mode in the pup skill (#109)" }
page.json+2−2
@@ -4,7 +4,7 @@   "slug": "pup-bridge",   "title": "Pup - Puppeteer Bridge",   "brief": "pup is the AI's own browser: a real, full Chrome on the user's desktop that the AI fully controls (a sandbox, not the user's signed-in browser). Rides Bridge; pup_* verbs open windows and tabs, navigate, screenshot, and eval JS.",-  "version": "2.0.489",+  "version": "2.0.490",   "tags": [     "skills",     "pup",@@ -167,5 +167,5 @@       "pup-bridge verbs are invoked through the adom-bridge CLI, not through a binary this package installs, so prefix rules cannot reach them."     ]   },-  "changelog": "extension-driven mode: correct tab targeting, liveness and close (#109)"+  "changelog": "teach extension-driven mode in the pup skill (#109)" }\ No newline at end of file