pi-chrome, patched to drive a signed-in browser on another host through a broker, with an MCP server https://git.soarez.net/sz/sz-chrome-remote-extension.git/atom?h=master 2026-05-13T11:29:41+00:00 2026-05-13T11:29:41+00:00 Tianren Dong tianrendong.dtr@gmail.com 2026-05-13T11:29:41+00:00 urn:sha1:4c54b05dc15b81e449dc8ac53da8bae536fa2798 2026-05-13T06:35:01+00:00 Tianren Dong tianrendong.dtr@gmail.com 2026-05-13T06:35:01+00:00 urn:sha1:26ab0d36e45b1b65f667d4743eb30e83389ff57f When a different Chrome extension (password manager, autofill popup, etc.) anchors an overlay to the focused input, Chrome's CDP refuses our Input.dispatchMouseEvent with 'Cannot access a chrome-extension:// URL of different extension'. The CDP target list shows the foreign chrome-extension:// URL as type:'other' attached to the same tab. New behaviour in cdp() wrapper: 1. On that specific error for any Input.* call, snapshot CDP targets to identify the offending extension id and log it (foreign-ext- detected event added to ring buffer). 2. Send Esc via Input.dispatchKeyEvent (key dispatch routes by focus, not coordinates, so it bypasses the overlay) to dismiss the popup. 3. Retry the original Input.* call once. 4. If retry still fails, throw a clear error naming the foreign extension id and listing three concrete workarounds: disable that extension on the page, use Tab-to-focus instead of clicking, or run /chrome quiet off.