Pup - the AI's own browser - Commit

by adom

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.

Overview Files Skills Discover Packages Releases Dependencies Issues15 Breadcrumbs Pull Requests Activity

← Commit history

WHY-CFT: image paths are resolved from the PAGE ROOT, not the markdown file directory, so they need the docs/ prefix

John Lauer ·fd111f332a ·2mo ago ·parent 187af3e

1 file changed +5−5

docs/WHY-CFT.md+5−5

@@ -36,11 +36,11 @@ When a browser is launched with `--enable-automation`, branded Chrome asserts an so any naive puppeteer script against branded Chrome wears the banner. It blips in and out as automation starts and stops, reflowing the viewport each time. -![Branded Chrome with --enable-automation](img/why-cft/banner-branded.png)+![Branded Chrome with --enable-automation](docs/img/why-cft/banner-branded.png)  Chrome for Testing, given the **exact same flag**, does not show it: -![Chrome for Testing with the same flag](img/why-cft/banner-cft.png)+![Chrome for Testing with the same flag](docs/img/why-cft/banner-cft.png)  > ### CORRECTION (2026-08-25) >@@ -51,7 +51,7 @@ Chrome for Testing, given the **exact same flag**, does not show it: > WebSocket session attached (`Page.enable`, `Runtime.enable`, `Runtime.evaluate`). No banner > appeared, and `navigator.webdriver` was `false`. >-> ![Branded Chrome, CDP attached, no banner](img/why-cft/banner-branded-cdp.png)+> ![Branded Chrome, CDP attached, no banner](docs/img/why-cft/banner-branded-cdp.png) > > The banner is keyed on the FLAG, not on the attach. So the honest version of this reason is: > puppeteer's default launch triggers it, and **pup strips the flag** (`ignoreDefaultArgs:@@ -85,7 +85,7 @@ page            Example Domain                                            https: service_worker  Service Worker chrome-extension://liomcalad.../worker.js  chrome-extension://liomcalad.../worker.js ``` -![CfT toolbar with the extension loaded](img/why-cft/ext-cft.png)+![CfT toolbar with the extension loaded](docs/img/why-cft/ext-cft.png)  **Branded Chrome 151: the extension is not there at all.** Same flag, same directory, five targets, and none of them is ours (the two extension entries are Google's OWN built-ins, Hangouts among them,@@ -99,7 +99,7 @@ browser_ui       Omnibox Popup      chrome://omnibox-popup.top-chrome/omnibox_po service_worker   Service Worker     chrome-extension://fignfifoniblkonapihmkfakmlgkbkcf/service_worker.js ``` -![Branded Chrome toolbar, no extension](img/why-cft/ext-branded.png)+![Branded Chrome toolbar, no extension](docs/img/why-cft/ext-branded.png)  We verified the fallout live on branded 148 back on 2026-08-10, trying every route to auto-install the Adom Pup toolbar: