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.
pup or native browser?
Adom gives an AI two ways to use a browser on your desktop. They solve different problems, and a good AI picks the right one for each task.
| pup | native browser (nb) | |
|---|---|---|
| whose browser | pup's own browser, its own windows | your own Chrome or Edge, your own windows |
| identity | the shared adom-you profile, which learns your logins over time | your real profile: your cookies, your single sign-on, your saved passwords |
| where windows appear | behind your work, labeled with the AI thread's name | wherever your browser puts them |
| control | total: open, close, navigate, type, click inside any frame, screenshot, record, run scripts | drives the page you are on, through the Adom browser extension |
| best for | testing your app, screenshots, scraping, recording, sign-ins pup has learned, anything the AI does on its own | handing a page to you, sites only your own browser is signed into, anything you will keep using yourself |
Why pup exists
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 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
Some things only your own browser has: the single sign-on session at your company, a site you signed into years ago and never in pup, a page you want to keep reading yourself. For those, an AI drives your real browser through the Adom browser extension's nbrowser_* commands, which is a separate bridge.
How to ask
- "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.
# pup or native browser?
Adom gives an AI two ways to use a browser on your desktop. They solve different problems, and a good AI picks the right one for each task.
| | pup | native browser (nb) |
|---|---|---|
| whose browser | pup's own browser, its own windows | your own Chrome or Edge, your own windows |
| identity | the shared adom-you profile, which learns your logins over time | your real profile: your cookies, your single sign-on, your saved passwords |
| where windows appear | behind your work, labeled with the AI thread's name | wherever your browser puts them |
| control | total: open, close, navigate, type, click inside any frame, screenshot, record, run scripts | drives the page you are on, through the Adom browser extension |
| best for | testing your app, screenshots, scraping, recording, sign-ins pup has learned, anything the AI does on its own | handing a page to you, sites only your own browser is signed into, anything you will keep using yourself |
## Why pup exists
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 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
Some things only your own browser has: the single sign-on session at your company, a site you signed into years ago and never in pup, a page you want to keep reading yourself. For those, an AI drives your real browser through the Adom browser extension's `nbrowser_*` commands, which is a separate bridge.
## How to ask
- "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.