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.
Restore after a browser restart can stall partway, leaving windows on disk (ConfRoomROG)
Summary
On ConfRoomROG (2.0.728, 2026-10-20 ~11:00 CDT) a pup_restart_browser saved 8 windows. Only 3 came back. Then the extension worker went silent: the log repeats "the extension channel did not answer a warm open and the worker is silent; relaunching the lane". The other 4 windows (OCP-OCuLink-riser, ranch-p1-motor-driver, ranch-p2-power, ranch-p6-charge) stayed on disk with no further restore attempt. A second pup_restart_browser brought back all 7 within 90 s.
The restart was fired by the new WebGL watchdog during a test: two forced GPU-process crashes, then the watchdog's restart. The restart code itself is the ordinary pup_restart_browser.
Log, in order
[restart] ... 8 window(s) and 9 tab(s) saved- webgl-test, aiflow-fields-043111, capencoder and mhs-cells-render come back
[recovery] "OCP-OCuLink-riser": ... relaunching (attempt 1)[recovery] "mhs-cells-render": could not quiet the restored tabs: the pup extension did not answer within 24s[lane] ... worker is silent; relaunching the lane, three times- nothing more for the 4 waiting windows
Mitigation in 2.0.728
The watchdog checks 3 minutes after its restart and restarts once more if any saved window is still waiting. A manual pup_restart_browser has no such check yet.
Asks
- Find why the worker goes silent mid-restore. Candidates: the restored media page (mhs-cells-render, a movie) hogging the worker, or the open path's own lane relaunch firing while a restore is still in flight.
- Make recovery keep retrying windows that are still on disk after a lane relaunch, instead of stopping.
0 Replies
Log in to reply.