← Commit history

how-pup-works: the extension lane is a long poll since 2.0.693

John Lauer ·147afc89d1 ·17d ago ·parent 66e9958
1 file changed +1−1
docs/how-pup-works.md+1−1
@@ -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 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.+pup drives each window through its own extension running inside the browser, which keeps a request open to pup and runs each command the moment pup hands it over (about a tenth of a second, since 2.0.693). 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