Signing the AI in to a site you already saved in Chrome is the worst flow in Hydrogen: needs a Logins & Cards screen and a never-foreground switch

by 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.

Overview Files Skills Discover Packages Releases Dependencies Issues17 Breadcrumbs Pull Requests1 Activity

Open feature request

Drew Owens · 12d ago

Filed at the user's request after a session on 2026-10-22 to 10-29 (Windows 11 laptop adom_drew2, pup-bridge 2.0.733 to 2.0.738, Adom Bridge 2.1.184+, Hydrogen). Their summary: "the worst UX in Hydrogen I've had in months". Each failure has its own issue; this one is the whole journey, which is the real bug.

The job

Let the AI pay vendor bills and place office orders as the user: sign in with the logins they already keep in Chrome, and pay with their work cards.

What it took

Logins. The first pup_import_browser_logins {} failed twice with no_data (app-bound encryption). A later filtered call worked for Costco and Amazon. Two days later Amex worked. Republic Services failed four times: once "no logins" because the wrong Chrome profile was read, three times with ab's own loopback timing out (separate issues). Meanwhile the user could plainly see the login in Chrome's password list and kept saying "I already gave you the creds".
Approvals with nothing on screen. consent_pending lasted minutes while the user saw no dialog. The AI sent a phone push asking them to approve a Windows Hello prompt that never appeared.
Cards. There is no UI for pup's card vault in Adom Bridge 2.1.184. Adding the work Visa and Amex took a PowerShell snippet the user pasted by hand. A .ps1 launched for them closed without saving.
Sign-in. On Amex, pup_login submit clicked the password "Show" toggle (separate issue).
Screen takeover. Out of options, the AI raised the pup window to ask the user to sign in themselves, while they were working. They asked it to stop, and it then retried the import, which also targets their screen.

What would fix the experience

A Logins & Cards screen in Adom Bridge or Hydrogen. It would list what pup's vault holds (hosts and usernames, never passwords). From it, the user could "Add from Chrome" with a profile picker and a per-site checkbox, and add a card. One place, no snippets.
Import failures in plain words, naming the profile read and how many logins it held, and returning in seconds. A prompt that should be on screen should be verifiable from the API, e.g. promptVisible:true.
A user-set "never foreground" switch (per machine, per thread) that makes raise/focus verbs refuse, so an AI cannot take the screen however stuck it is.
A guarded fallback: when the vault has no login for a site, offer the user a one-click "send this one login from Chrome to pup" from their own browser (the nb extension already lives there), rather than the AI driving Chrome's export.

Pup - the AI's own browser