pup_import_browser_logins reads the wrong Chrome profile, reports 'no logins', and has no way to choose the profile

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 bug report

Drew Owens · 12d ago

pup-bridge 2.0.738 · native-browser (nb) bridge 0.16.60 · Windows 11 laptop (adom_drew2) with three Chrome profiles: Default ([email protected], shown as "Work"), Profile 3 ([email protected]), Profile 6 ([email protected]).

What happens

pup_import_browser_logins {"hostFilter":["republicservices"]}
-> ok:false, "nb's export contained no logins. The exported profile may have no saved passwords. Check nbrowser_profiles for the right profile."

The login was saved, in the Work profile's Google Password Manager (republicservices.com, next to amazon.com, americanexpress.com and costco.com). The export came back with zero rows in total, so it read some other profile.

pup_import_browser_logins takes only browsers and hostFilter. There is no way to say which profile to export.
The answer doesn't say which profile was read, so neither the AI nor the user can tell it went to the wrong one.
The hint says "check nbrowser_profiles", but even with the right profile name in hand there is nothing to pass it to.

Related: the nb issue "nbrowser_open_window without a profile silently uses the active one; refuse when several identities are connected" is the same failure in another verb.

Expected

A profile argument (an email or profile dir), defaulting to the profile that holds the user's work identity, or refusing when several are connected.
The answer names the profile that was read and the number of logins it held before the filter, e.g. read chrome:[email protected]: 0 logins rather than "no logins".

1 Reply

Colby Knox · 5d ago

pup 2.0.741 (public) adds two things for this:

pup_import_browser_logins {profile:"chrome:[email protected]"} names the browser profile to read, using the keys nbrowser_profiles lists. It also works with sessionFor.
The answer carries profile when nb reports which profile it read. no_data says which profile came back empty and how to name another.

Tested: the profile key reaches nb, and with it a site session went from a real Chrome 156 profile into pup.

Not tested: a password export from a machine with several real Chrome profiles like yours, because the test machine has no saved passwords in a profile nb can reach.

Could you try {"hostFilter":["republicservices"],"profile":"chrome:[email protected]"} once you have 2.0.741 and say whether the Work profile's logins come over? I'll leave this open until then.