Pup - the AI's own browser
Public Made by Adomby 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.
e1a9528
18d ago
Install size and footprint
What pup puts on your machine, measured, what cleans itself up, and how to remove it.
What you download
| piece | size | when |
|---|---|---|
pup itself (adom-pup-bridge.exe, signed) |
4 MB download, 8.4 MB on disk | The first time an AI asks for a browser. Adom Bridge fetches it and checks its sha256. |
| pup's browser build | 200 MB download, 428 MB unpacked | Once, in the background, right after install. Until it lands, pup uses your installed Chrome or Edge, so the first window does not wait. |
| AI skills (in a container) | under 1 MB | adom-wiki pkg install adom/pup-bridge |
On a brand-new Windows machine (measured 2026-09-23): pup installed in 1 second, was usable at once on the system Edge, finished the browser download in 6 seconds and unpacking in 3, and opened its first window 24 seconds after a bare install.
What grows with use
Measured on a desktop used heavily for a month (2026-10-03):
| location | size | what it is |
|---|---|---|
%LOCALAPPDATA%\Adom Bridge\bridges-cache\puppeteer |
15 MB | the program, recent screenshots |
~/.cache/puppeteer |
428 MB | the browser build, exactly one copy |
~/.adom/pup-profiles/adom-you |
1.1 GB | the shared profile: cookies, logins, site data and cache for every site you use in pup |
~/.adom/pup-profiles (all) |
4.0 GB | adom-you plus 20 older named profiles |
~/.adom/pup-logs |
3 MB | the log, capped at 2 MB with one rotation |
~/.adom/pup-vault.bin |
under 1 MB | the encrypted vault |
The adom-you profile grows like any browser profile: mostly the cache of the sites you visit.
What cleans itself up
- Browser builds. A minute after each start pup deletes superseded browser builds and leftover partial downloads. It keeps only the build in use, never touches one a running browser uses, and waits for any download in progress. Before this (2.0.677), every update kept the old 410 MB build forever.
- Throwaway profiles. Profiles made for
isolated:truewindows are deleted with their window and swept at each start. - Taskbar registrations. Each window's taskbar identity is removed when it closes, and leftovers are swept at start.
- Screenshots and recordings are kept for a limited time and size.
What does not clean itself up yet: named profiles. A profile created for one task (a profile:"name" open) stays until it is removed, which is how the measured desktop collected 20 of them and 2.9 GB. To reclaim that space, ask your AI to "reap pup's idle profiles". It runs pup_reap_profiles {"dryRun":true} to list profiles idle for 14 days, then the same without dryRun to delete them. It never deletes adom-you, a profile that is open, or one needed to restore a saved window.
Removing pup
pup_uninstall {"confirm":true}removes pup's profiles and saved windows, its staged extensions, its taskbar icons and every taskbar identity it registered. It keeps your saved logins; remove those withcredential_delete.- Adom Bridge's
bridge_uninstall {"name":"puppeteer"}removes the program. - The browser build in
~/.cache/puppeteercan be deleted by hand afterwards.
# Install size and footprint
What pup puts on your machine, measured, what cleans itself up, and how to remove it.
## What you download
| piece | size | when |
|---|---|---|
| pup itself (`adom-pup-bridge.exe`, signed) | 4 MB download, 8.4 MB on disk | The first time an AI asks for a browser. Adom Bridge fetches it and checks its sha256. |
| pup's browser build | 200 MB download, 428 MB unpacked | Once, in the background, right after install. Until it lands, pup uses your installed Chrome or Edge, so the first window does not wait. |
| AI skills (in a container) | under 1 MB | `adom-wiki pkg install adom/pup-bridge` |
On a brand-new Windows machine (measured 2026-09-23): pup installed in 1 second, was usable at once on the system Edge, finished the browser download in 6 seconds and unpacking in 3, and opened its first window 24 seconds after a bare install.
## What grows with use
Measured on a desktop used heavily for a month (2026-10-03):
| location | size | what it is |
|---|---|---|
| `%LOCALAPPDATA%\Adom Bridge\bridges-cache\puppeteer` | 15 MB | the program, recent screenshots |
| `~/.cache/puppeteer` | 428 MB | the browser build, exactly one copy |
| `~/.adom/pup-profiles/adom-you` | 1.1 GB | the shared profile: cookies, logins, site data and cache for every site you use in pup |
| `~/.adom/pup-profiles` (all) | 4.0 GB | adom-you plus 20 older named profiles |
| `~/.adom/pup-logs` | 3 MB | the log, capped at 2 MB with one rotation |
| `~/.adom/pup-vault.bin` | under 1 MB | the encrypted vault |
The adom-you profile grows like any browser profile: mostly the cache of the sites you visit.
## What cleans itself up
- **Browser builds.** A minute after each start pup deletes superseded browser builds and leftover partial downloads. It keeps only the build in use, never touches one a running browser uses, and waits for any download in progress. Before this (2.0.677), every update kept the old 410 MB build forever.
- **Throwaway profiles.** Profiles made for `isolated:true` windows are deleted with their window and swept at each start.
- **Taskbar registrations.** Each window's taskbar identity is removed when it closes, and leftovers are swept at start.
- **Screenshots and recordings** are kept for a limited time and size.
**What does not clean itself up yet: named profiles.** A profile created for one task (a `profile:"name"` open) stays until it is removed, which is how the measured desktop collected 20 of them and 2.9 GB. To reclaim that space, ask your AI to "reap pup's idle profiles". It runs `pup_reap_profiles {"dryRun":true}` to list profiles idle for 14 days, then the same without `dryRun` to delete them. It never deletes adom-you, a profile that is open, or one needed to restore a saved window.
## Removing pup
- `pup_uninstall {"confirm":true}` removes pup's profiles and saved windows, its staged extensions, its taskbar icons and every taskbar identity it registered. It keeps your saved logins; remove those with `credential_delete`.
- Adom Bridge's `bridge_uninstall {"name":"puppeteer"}` removes the program.
- The browser build in `~/.cache/puppeteer` can be deleted by hand afterwards.