Pup - the AI's own browser

Install?

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 — 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) — 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.

adom-wiki pkg install adom/pup-bridge

Latest: v2.0.733, published

Download for your machine · v2.0.733?

Release 2.0.733

Family

Dependencies 1 app

Contents

README

markdown

pup: the AI's own browser

pup gives your AI a real browser on your desktop that it drives completely, in the background, signed in as you. It opens real Chrome windows that never jump in front of your work, keeps one shared profile where your logins accumulate, fills saved passwords for the AI, and labels every window on the taskbar with the name of the AI thread that owns it. Ask your AI to "open it in pup" and it does.

pup is one small signed Windows program (about 8 MB) that 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

A prompt typed into a Claude thread in Hydrogen, then pup doing the work on a real Windows desktop: Texas Instruments' TPS54202, ST's L6981 and MPS's MP2338 on the makers' own sites, the footprint on Component Search Engine, a screenshot and a recorded clip, then a board on the Adom wiki in 3D flipped to the public view. Along the way: taskbar buttons named after each AI 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:

adom-wiki pkg install adom/pup-bridge

Quick start

Your AI addresses its windows by its own thread name, so there are no ids to track:

adom-bridge --ai-thread "my-thread" pup_open_window '{"url":"https://example.com"}'   # a real window, behind your work
adom-bridge --ai-thread "my-thread" pup_screenshot  '{}'                              # the image lands in the container
adom-bridge --ai-thread "my-thread" pup_navigate    '{"url":"https://wiki.adom.inc"}' # same window, next page
adom-bridge --ai-thread "my-thread" pup_my_windows  '{}'                              # everything this thread has open

Or just say it: "open my app in pup", "screenshot this site in pup", "record a clip of this page in pup".

Every window wears its thread's name

pup thread tiles on the Windows taskbar, each with its page's favicon badge

Each AI thread gets one taskbar button, and its icon is the thread's name drawn on the Adom teal tile. All of that thread's windows group under it, so the taskbar reads as a list of your threads, not a row of identical browser icons. The small badge in the corner is the active tab's own favicon: above, spice-compare is on a Texas Instruments page, nsf-proposal on the Adom wiki, parts-search on GitHub, and my-app on an ordinary site. pup stamps the name before the window first appears, so a button never starts out as a plain browser icon and changes later. Details, the five other display modes, and how to switch: Taskbar identity and jump lists.

Right-click a tile for pup's tasks

The jump list on a pup wiki window: switch views, annotate, open the dashboard, close all

Right-clicking a pup tile opens its jump list. Every window offers Annotate this page (draw on the page and the marked-up capture goes to the owning AI thread), Open pup dashboard, and Close ALL Adom Pup windows. An Adom wiki window adds Switch to logged-in view and Switch to public view, which flips the same window between what you see and what the public sees, the fastest way to check what a publish exposes. Each task runs pup's own signed program directly, with no script in between.

The dashboard shows every window, live

The pup dashboard: live windows grouped by AI thread, the taskbar mirror, and why each icon looks the way it does

The dashboard lists every pup window grouped by the AI thread that owns it, with each tab, whether it is signed in, which profile it surfs on, and a mirror of the taskbar buttons. Every icon carries a "how this icon was chosen" note, so a wrong icon is never a mystery. The Say it panel lists phrases you can paste into any AI thread, and the gear opens Settings. Open it from the dock bar card, the jump list, or by asking your AI for "your dashboard in pup". Full tour: The dashboard.

Feature guides

guide what it covers
How pup works One signed exe, the extension lane, windows born behind your work, the shared adom-you profile, restarts and upgrades, and what is never brought back.
Taskbar identity and jump lists Thread tiles, favicon badges, the six display modes, jump list tasks, and the Start Menu anchor setting.
The dashboard The live window map, the taskbar mirror, icon explanations, Say it, and the toolbar buttons.
Settings Every setting in the Settings window, its default, and what it changes.
Logins, passwords and cards pup's own vault, auto-capture and fill, reason-gated sign-in, importing from Chrome or Edge, Google accounts, Basic-Auth, cards.
Screenshots and recording Window, element and full-page screenshots, recording with sound, and annotate.
Install size and footprint What lands on disk, measured, what cleans itself up, and how to remove pup completely.
pup or native browser? When the AI should use pup, when it should drive your own browser, and why both exist.
Open source: code and contributing How the code is organized, how to build and test it, how to add a feature, and how to send it back.
Why pup uses its own browser build The dated record of that decision.

Talk to the AI

you want say
see your app "open my app in pup"
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 digikey in pup"
everything open "what do you have open in pup?"
the dashboard "open your dashboard in pup"

Dependencies

dependency required? why
Windows 10 or 11 yes pup is a native Windows program. A Mac port is in progress; Macs run the older build for now.
Adom Bridge 2.1 or later yes It installs, updates and starts pup, and carries every command from your AI to it. Hydrogen includes it.
A browser build automatic pup downloads its own Chrome build once (about 200 MB, 428 MB unpacked) and uses your installed Chrome or Edge until that finishes.

Skills

The skills teach any AI how to use pup well. The main pup skill is the start; the others load when a task needs them.

skill purpose
pup Start here: the model, addressing by thread name, the everyday verbs, and the rules.
pup-windows-sessions-tabs Windows, tabs, ownership and the zero-id forms.
pup-screenshots-recording Every screenshot and recording option, and tricky pages.
pup-credentials The vault, sign-in, imports and Google accounts.
pup-lanes How pup drives a window and the rules that keep your closes final.
pup-taskbar-states The six taskbar display modes, exactly.
pup-settings Every setting, behavior by behavior.
pup-adom-wiki Viewing wiki pages signed in or as the public.
pup-vendor-login Signing into vendor portals.
pup-browsers-and-chrome Readiness, the browser build and cold starts (maintainer detail).

Open source

The complete source is in this page's Files tab: one Rust workspace of twelve crates, with every Windows call kept in a single crate so the Mac port only implements one interface. Open source: code and contributing walks through the layout, the build, the tests and the release gates, and how to send a change back as a pull request on this page. Issues and ideas are welcome in the Issues tab.