Pup - the AI's own browser

@@ -4,6 +4,12 @@  pup is one small signed Windows program (about 8 MB) that [Adom Bridge](https://wiki.adom.inc/adom/adom-bridge) installs and keeps up to date for you. This page holds its source, its AI skills, and the guides below. It is open source under the MIT license. +## Watch the two-minute tour++<video controls preload="metadata" poster="docs/img/tour-poster.jpg" src="docs/video/pup-tour.mp4"></video>++Two AI threads at work on a real Windows desktop: one checks a Texas Instruments buck converter against LCSC and DigiKey, takes a screenshot and records a clip; the other opens a board on the Adom wiki in 3D and flips it to the public view. Along the way: taskbar buttons named after each thread, favicon badges that follow the active tab, the right-click jump list, the dashboard, and Settings.+ ## Install  On your desktop there is nothing to install by hand. Adom Bridge (bundled with Hydrogen) downloads pup the first time an AI asks for a browser, and updates it on its own. In an AI container, install the skills so the AI knows how to use it:@@ -66,7 +72,7 @@ The dashboard lists every pup window grouped by the AI thread that owns it, with | check a page | "screenshot this site in pup" | | a clip | "record a clip of this page in pup" | | the public view of a wiki page | "show me the logged-out view in pup" |-| sign in | "log me into mouser in pup" |+| sign in | "log me into digikey in pup" | | everything open | "what do you have open in pup?" | | the dashboard | "open your dashboard in pup" | 

@@ -425,6 +425,9 @@ refuses, or when the task genuinely needs the user's identity. 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.+**Update 2026-10-03:** that fixed the debug-port blocks, but Mouser, Arrow, Octopart and Newark also run+bot walls that come and go (Akamai "Access Denied", 403) even on the extension lane. Check the page+text for denied/captcha before trusting a load, and fall back to DigiKey, LCSC or TI, which loaded reliably. 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

@@ -23,7 +23,7 @@ Adom Bridge on your desktop ── starts, updates and talks to ──▶ adom-p  pup opens real browser windows, not a hidden headless engine, so screenshots and recordings show exactly what a person would see. It uses its own Chrome build so it can load its extension and stay on a known version; until that build has downloaded on a new machine, pup uses your installed Chrome or Edge. The [why pup uses its own browser build](WHY-CFT.md) record has the full reasoning. -pup drives each window through its own extension running inside the browser, which polls pup for commands and runs them. This is the **extension lane**, and it is the only way pup opens windows by default. There is no remote debugging port, which matters: vendor sites such as st.com, Mouser and Arrow detect a debug port and block the page, and through the extension lane they load normally. The extension lane handles trusted mouse and keyboard input (including inside cross-site frames), element and full-page screenshots, downloads, fetching files with the page's cookies, and HTTP Basic-Auth from the vault. An older debugging lane still exists for the rare feature that needs it, and it is off unless a person turns it on for a machine.+pup drives each window through its own extension running inside the browser, which polls pup for commands and runs them. This is the **extension lane**, and it is the only way pup opens windows by default. There is no remote debugging port, which matters: vendor sites such as st.com detect a debug port and block the page, and through the extension lane they load normally. (A few sites, such as Mouser and Arrow, also run separate bot walls that can refuse any automated browser on some days; measured 2026-10-03, TI, DigiKey and LCSC loaded while Mouser and Arrow were walled.) The extension lane handles trusted mouse and keyboard input (including inside cross-site frames), element and full-page screenshots, downloads, fetching files with the page's cookies, and HTTP Basic-Auth from the vault. An older debugging lane still exists for the rare feature that needs it, and it is off unless a person turns it on for a machine.  ## Windows are born behind your work 

⋯ 1 unchanged line ⋯

@@ -14,7 +14,7 @@ Adom gives an AI two ways to use a browser on your desktop. They solve different  A normal browser is built for a person. It asks you to save a password, pick a saved login, click a cookie banner, bring a window forward. An AI driving your own browser keeps tripping over that machinery, and it competes with you for the same windows and tabs. -pup is a browser built for the AI. It does all of that silently, in windows you can ignore, and it never touches the tabs you are using. Because every pup window shares the adom-you profile, logins you make in pup accumulate, so pup can sign into more of your sites over time. And because pup drives its browser through its own extension rather than a debugging port, vendor sites that block automation (st.com, Mouser, Arrow) load normally.+pup is a browser built for the AI. It does all of that silently, in windows you can ignore, and it never touches the tabs you are using. Because every pup window shares the adom-you profile, logins you make in pup accumulate, so pup can sign into more of your sites over time. And because pup drives its browser through its own extension rather than a debugging port, vendor sites that block a debugging port (st.com is the classic case) load normally, along with TI, DigiKey and LCSC. A few sites, such as Mouser and Arrow, also run bot walls that sometimes refuse any automated browser; pup reports that page as blocked rather than pretending it loaded.  ## Why native browser exists @@ -22,7 +22,7 @@ Some things only your own browser has: the single sign-on session at your compan  ## How to ask -- "open my app in pup", "screenshot this in pup", "log me into mouser in pup": pup.+- "open my app in pup", "screenshot this in pup", "log me into digikey in pup": pup. - "open this in my browser", "show it to me in Chrome": native browser.  When in doubt, an AI uses pup: it is safe to run while you work and leaves your own browser alone.

⋯ 1 unchanged line ⋯