open_window succeeds but the tab stays on the extension's birth.html; eval/navigate then fail

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

Closed bug report

John Lauer · 22d ago ·closed by John Lauer

2026-10-19 ~11:50–12:10Z, AdomLapper and ConfRoomROG (Windows 11, Chrome for Testing 152.0.7977.82, extension lane; the CDP lane is off on AdomLapper).

pup_open_window {"url":"https://wiki.adom.inc/john/capacitive-encoder","sessionId":"capclips2"} returns success, but the tab never leaves the extension's start page. A pup_eval 12–15 s later fails with:

Cannot access contents of url "chrome-extension://liomcaladmooagjiebkfgegciadapnpi/birth.html?token=idjvnf6amvf77bjj". Extension manifest must request permission to access this host.

pup_navigate on such a window times out at ab's 60 s budget. It reproduced with three fresh windows on AdomLapper and one on ConfRoomROG; pup_readiness said a drivable browser exists. A screenshot of one window was a blank dark page. (At the same time wiki.adom.inc page routes were hanging, adom/wiki#231, which may be why the first navigation never completed, but pup reported success and left the window on birth.html instead of saying the navigation failed.)

Expected: open_window reports the navigation failure/timeout, and eval explains that the tab is still on pup's own start page.

1 Reply

John Lauer · 21d ago

Fixed on insiders (2.0.725, refined in 2.0.727). The cause: when the navigate after birth answered but the tab never left birth.html, pup recorded the birth page as the window's address, so nothing could send it on, and the open reported success. Now:

The birth page is never recorded over a real address (live tab sync, tab refresh, both open paths, re-adoption after a restart).
The open retries the navigate once and logs when the tab is still on the birth page.
The health check sends any window still on its birth page 20 s after birth to its recorded address (up to 3 tries). Proven end to end on ConfRoomROG: a window held on its birth page across a restart was re-adopted and sent to its address on the first try.
2.0.727 also makes the birth page explain itself while a slow site loads (which thread opened it, why, where it is going, how long it has waited), and retitles the tab 'Opening for (pup)' after 10 s.

John Lauer closed this · 21d ago