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 has no payment-card vault, so the AI cannot complete a checkout it has otherwise filled in
What is missing
pup's credential vault stores login credentials only: credential_set, credential_list, credential_delete (HTTP Basic Auth / site passwords into the OS keychain), plus desktop_decrypt_browser_credentials for importing the user's saved browser passwords.
There is no equivalent for payment cards. A normal Chrome profile keeps cards in a separate autofill store (Web Data -> credit_cards, encrypted with the same OS key as passwords) and offers them at checkout. pup drives Chrome for Testing in a pup-managed durable profile, but exposes no way to store, list, or autofill a card.
Why it matters
This is the point at which pup stops being an assistant. Today an AI can do the entire job for the user, then stall on the last click:
Real case, 2026-09-02. John asked for a Venture Dallas conference ticket. pup opened the checkout, selected the correct $350 Entrepreneur Pass, filled first/last name, email, mobile, accepted terms, and advanced to the Stripe payment step. Then it could go no further, because there is no card. The only options were to hand the laptop back to the user or ask him to paste a card number into chat, which is worse than either alternative.
The user's framing: "pup's whole point of existing is that it can do stuff for me via the AI. Does pup store credit cards just like a normal Chrome browser does? It should."
Requested behaviour
card_set/card_list/card_delete, mirroring the credential verbs. PAN + expiry + CVV into the OS keychain;card_listreturns only nickname, brand, last four and expiry, never the PAN or CVV, exactly ascredential_listnever returns a password.- Autofill a stored card into a checkout form on request, addressed by nickname (e.g.
adom-amex), so the AI never handles the digits. - A per-fill approval gate. A card is not a password: the natural default is that each use prompts the human once, in the moment, with merchant and amount shown. An always-allow-this-merchant option would be a bonus, not the default.
- Optionally extend
pup_import_browser_loginsto import cards from the user's own Chrome/Edge profile, behind the same consent + UAC flow that already exists for passwords.
Notes
- Approval UX matters more here than for passwords. The gate should show merchant, amount and last four so the human is approving a specific charge, not a vague capability.
- Scope it to autofill into a page pup is already driving. Nothing should be able to read a PAN back out through a verb.
- Related:
john/work->work-amexdocuments the Adom Amex account but deliberately holds no card data and forbids payments without explicit approval. A pup card vault plus a per-charge prompt is what would let that skill actually authorise a payment safely.