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.
pup_input_dispatch accepts advertised selector but silently clicks viewport 0,0
Versions: Adom Bridge CLI 2.1.96 (541e1f0c-dirty), ConfRoomROG Puppeteer bridge 2.0.464, Chrome for Testing 148.0.7778.97, Windows desktop. First observed 2026-09-11; no claim about earlier runtime behavior.
adom-bridge help pup_input_dispatch advertises selector for type=click, including cardinality validation and a clickedRect result. The live bridge accepts the documented selector argument but silently clicks viewport (0,0), returning ok:true and dispatched:click.
Input (explicit task-owned session/tab):
{"sessionId":"depthlab-sourcing","tabId":"tab-1","type":"click","selector":"a[href$=\"/cr0402.stp\"]"}
Expected: click the matching link or reject unsupported selector input with a usable hint. Actual significant response fields:
{"ok":true,"status":"ok","dispatched":"click","x":0.0,"y":0.0,"sessionId":"depthlab-sourcing","tabId":"tab-1"}
The page was the Bourns CR0402 design-file listing; the link was visibly present. A subsequent DOM bounding-box measurement gave center (303.640625,445.5). Supplying those explicit coordinates successfully opened the file link in a new tab. This establishes a selector/help/runtime mismatch, separate from the manufacturer's security-verification response at the file URL.
Please make help and live schema agree, implement selector targeting or reject unsupported/missing coordinates, and never default a documented selector-only click to (0,0). Return AI hints for the supported targeting mode and actual matched element. No foreground activation was used. Screenshot shows the original listing and visible file link.
