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
Logins, passwords and cards
pup keeps its own password manager so your AI can sign into sites as you, in the background, without the browser's save-password bubbles and autofill dropdowns that are built for a person at the keyboard. This guide covers how logins are captured, filled and protected, and how pup handles payment cards.
Where secrets live
Passwords are stored in one file per Windows user, ~/.adom/pup-vault.bin, encrypted with Windows' own data protection (DPAPI), so only your Windows account on this machine can read it. Card numbers live in the same kind of store. No pup command ever returns a password or card number to a cloud AI, and pup never writes one to a log.
Captured as you sign in
When you sign into a site in a pup window, pup saves the username and password as the form is sent. The next command the AI runs tells it that a login was captured. Because every pup window shares the adom-you profile, each login you make anywhere makes pup better at signing in everywhere. Turn capturing off in Settings if you prefer.
Filled on return, sent only with a reason
When a pup window reaches a sign-in page for a site the vault knows, pup fills the saved username and password in the background. It never sends the form by itself. An AI must call pup_login with submit:true and a submitReason explaining why this site is the right one; pup echoes the real address back, so a look-alike or redirected domain is caught before a password goes anywhere. A login that matches several accounts asks which one.
Every open and navigate also reports where the window landed: whether it is a sign-in page, whether a login is offered, and whether the profile is already signed in. So an AI never asks you to sign in where you already are.
Bringing in the logins you already have
- From Chrome or Edge.
pup_import_browser_loginscopies your saved passwords from your own Chrome, Edge or Brave on this machine into pup's vault, after one consent dialog and one Windows administrator prompt. It runs only on your desktop, never from a cloud AI. - From your other desktop.
pup_vault_syncmerges the logins of two of your desktops in both directions, newest wins. Passwords travel pup to pup and never pass through an AI. - By hand.
credential_setstores one login;pup_credentialslists what is stored as host and username only;credential_deleteremoves one.
Google accounts
pup_google_accounts lists the Google accounts found in your browsers and in pup's vault, marked work or personal, and whether pup is already signed in to each. pup_google_signin signs in as a named account hands-free. When Google asks for a second step, it hands back the options and the exact call to finish with the code, and it never restarts a sign-in that is waiting for a code.
HTTP Basic-Auth
Some vendor and intranet pages ask for a username and password in a browser dialog instead of a web form. pup answers those from the vault through its extension, with no dialog. When the vault has no login for that site, the AI gets a clear no_credential error naming the host, instead of a page that seems to hang.
Seeing a password
pup_credential_reveal shows one saved login to a program running on your own desktop, and only after you click a consent notice on your screen. One site per call, never in bulk, and refused outright for cloud AIs.
Payment cards
pup_card_set stores a card under a nickname. pup checks the number, expiry and security code, and no command ever returns them afterward. An AI should ask you for card details and never copy them from a page. pup_fill_card types a saved card into a checkout page, including the payment fields that live in Stripe-style frames, without the digits ever reaching the AI. It answers only with which fields it filled. Every fill waits for your approval on a desktop notice that names the merchant.
# Logins, passwords and cards
pup keeps its own password manager so your AI can sign into sites as you, in the background, without the browser's save-password bubbles and autofill dropdowns that are built for a person at the keyboard. This guide covers how logins are captured, filled and protected, and how pup handles payment cards.
## Where secrets live
Passwords are stored in one file per Windows user, `~/.adom/pup-vault.bin`, encrypted with Windows' own data protection (DPAPI), so only your Windows account on this machine can read it. Card numbers live in the same kind of store. No pup command ever returns a password or card number to a cloud AI, and pup never writes one to a log.
## Captured as you sign in
When you sign into a site in a pup window, pup saves the username and password as the form is sent. The next command the AI runs tells it that a login was captured. Because every pup window shares the adom-you profile, each login you make anywhere makes pup better at signing in everywhere. Turn capturing off in [Settings](settings.md) if you prefer.
## Filled on return, sent only with a reason
When a pup window reaches a sign-in page for a site the vault knows, pup fills the saved username and password in the background. It never sends the form by itself. An AI must call `pup_login` with `submit:true` and a `submitReason` explaining why this site is the right one; pup echoes the real address back, so a look-alike or redirected domain is caught before a password goes anywhere. A login that matches several accounts asks which one.
Every open and navigate also reports where the window **landed**: whether it is a sign-in page, whether a login is offered, and whether the profile is already signed in. So an AI never asks you to sign in where you already are.
## Bringing in the logins you already have
- **From Chrome or Edge.** `pup_import_browser_logins` copies your saved passwords from your own Chrome, Edge or Brave on this machine into pup's vault, after one consent dialog and one Windows administrator prompt. It runs only on your desktop, never from a cloud AI.
- **From your other desktop.** `pup_vault_sync` merges the logins of two of your desktops in both directions, newest wins. Passwords travel pup to pup and never pass through an AI.
- **By hand.** `credential_set` stores one login; `pup_credentials` lists what is stored as host and username only; `credential_delete` removes one.
## Google accounts
`pup_google_accounts` lists the Google accounts found in your browsers and in pup's vault, marked work or personal, and whether pup is already signed in to each. `pup_google_signin` signs in as a named account hands-free. When Google asks for a second step, it hands back the options and the exact call to finish with the code, and it never restarts a sign-in that is waiting for a code.
## HTTP Basic-Auth
Some vendor and intranet pages ask for a username and password in a browser dialog instead of a web form. pup answers those from the vault through its extension, with no dialog. When the vault has no login for that site, the AI gets a clear `no_credential` error naming the host, instead of a page that seems to hang.
## Seeing a password
`pup_credential_reveal` shows one saved login to a program running on your own desktop, and only after you click a consent notice on your screen. One site per call, never in bulk, and refused outright for cloud AIs.
## Payment cards
`pup_card_set` stores a card under a nickname. pup checks the number, expiry and security code, and no command ever returns them afterward. An AI should ask you for card details and never copy them from a page. `pup_fill_card` types a saved card into a checkout page, including the payment fields that live in Stripe-style frames, without the digits ever reaching the AI. It answers only with which fields it filled. Every fill waits for your approval on a desktop notice that names the merchant.