sz-chrome-remote-extension.git/broker, branch master 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-11-06T09:20:16+00:00 broker: refuse uploads from outside the staging directory 2026-11-06T09:20:16+00:00 Igor Soarez igor@soarez.org 2026-11-06T09:20:16+00:00 urn:sha1:85b49885256464b735923eaa771044706383718f page.upload and a raw DOM.setFileInputFiles through cdp.call now have to name files whose real path is under /tmp/pi-chrome-uploads (PI_CHROME_UPLOAD_DIR), on the broker's host. Anyone holding the token could otherwise attach any file the user can read to a page. broker: a standalone bridge for the browser's host 2026-10-14T11:15:57+00:00 Igor Soarez igor@soarez.org 2026-10-14T11:08:17+00:00 urn:sha1:f2e93bba02734461b4e40a1a2684372e6f2437c7 Upstream's bridge lives inside whichever pi session started first on the machine running the browser, and only serves that machine. The broker takes its place permanently: upstream's HTTP contract to the extension on loopback, and /command and /status on a second, private address for other hosts, behind a bearer token (PI_CHROME_TOKEN, or PI_CHROME_TOKEN_COMMAND).