pup_import_browser_logins: callback to ab loopback 127.0.0.1:24680 times out (nb_call_failed) after minutes of consent_pending with no prompt on screen

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, extension 0.2.15 in both connected Chrome profiles (bridge expects 0.2.22) · Adom Bridge 2.1.18x · Windows 11 laptop (adom_drew2), called over the relay from a cloud container.

What happens

pup_import_browser_logins fails before Chrome is ever asked for anything:

adom-bridge --target adom_drew2 --ai-thread Facility pup_import_browser_logins '{"hostFilter":["republicservices"],"browsers":["chrome"]}'

"ok": false,
"errorCode": "nb_call_failed",
"error": "Could not reach the native-browser bridge (nb) to export saved logins: ab loopback API unreachable: http://127.0.0.1:24680/command: Network Error: Network Error: Error encountered in the status line: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (os error 10060)"

%USERPROFILE%\.adom\direct-api-port reads 127.0.0.1:24680, so pup is calling the right address. ab simply does not answer pup's callback in time.
Three calls on 2026-10-29 ended this way, each after first returning consent_pending ("Waiting for the import to finish on the user's desktop") for a few minutes. The user saw no Chrome export dialog and no Windows Hello prompt at any point, so consent_pending was waiting on nothing.
nbrowser_readiness at the same moment: ready: true, extensionConnected: true.
The same verb worked on 2026-10-27 (hostFilter:["americanexpress"], 1 added, 9 s).

My guess: ab's loopback is busy dispatching the very pup_import_browser_logins call that pup is calling back from, so the nested call to nb never gets a turn. The stale extension could also matter, but the error is at the ab loopback, not in nb.

Expected

The callback reaches nb, Chrome's export runs, and the verb returns counts. If ab cannot be reached, fail in seconds with that reason, not after minutes of consent_pending that sends the user hunting for a prompt that does not exist.

Why it matters

The user had saved the login in Chrome specifically so the AI could take it, and lost most of an afternoon to this. In their words: "the worst UX in Hydrogen I've had in months".

Pup - the AI's own browser