Pi Bridge

Setup Pi Bridge requires an existing Pi CLI installation. 1. Install Pi Bridge from the Chrome Web Store in each Chrome profile you want Pi to control. 2. In your Pi Agent, install the companion package: pi install git:github.com/GHChrisSu/pi-browser-bridge 3. Restart Pi or run /reload to load the browser tools. The Chrome extension and the Pi package are installed separately. Pi Bridge connects the Pi coding agent running on this computer to Chrome. It is an independent community project and does not install Pi. Version 0.8.0 lets multiple Pi sessions using the same Pi agent directory share one local broker. Browser writes are serialized per Chrome profile, and connection status is clearer. With Pi and the Pi Bridge extension installed, you can ask Pi to: - Read visible page text and inspect interactive elements in the active tab or a selected background tab. - Open background tabs and organize them into Pi Bridge workspaces without moving existing tabs or changing the selected tab. - Read up to five web pages in temporary background tabs, then close them. - Navigate, click, fill ordinary form fields, press keys, scroll, and wait for page updates. - Find controls by accessible role and name, inspect accessible nodes, and click a node with a browser-level pointer event. - List visible images, media, and download links. Download selected page assets or a specified HTTP/HTTPS URL to your local Downloads folder. - Upload one local file up to 50 MiB to a page after you approve the file and destination in Pi. - Capture the visible tab. Pi Bridge does not change Chrome focus to capture a background tab. Each Chrome profile has a stable local profile ID and an optional short label. Multiple Pi sessions using the same Pi agent directory can share one local broker. Browser writes are serialized within each profile. When multiple profiles are connected, pass the intended profile_id so Pi Bridge never silently chooses the wrong profile. Privacy and safety: Page text, titles and URLs, accessible labels, selected control metadata, tab and workspace metadata, and screenshots are returned to Pi on this computer. Pi may include that content in requests to the model provider configured by the user. The extension stores a random profile ID and optional label in that Chrome profile's extension storage. It sends these values to the local Pi process for profile routing; they are not sent to the project maintainer or a remote bridge server. The extension does not read website cookies, site local or session storage, or password and hidden-input values. It refuses to fill password, hidden, file, and token-like fields. Visible page content and screenshots may still contain sensitive information. Download results include a local path and basic metadata. Direct HTTP/HTTPS downloads use Chrome's Downloads API and may send the profile's cookies to the destination host. When you upload a file, Chrome sends it directly to the selected website after you confirm the file and destination. Pi Bridge's project servers receive no copy of the file. The extension uses fixed, packaged browser operations and does not execute model-supplied JavaScript. Chrome restricts extensions on some pages, including browser-internal pages and the Chrome Web Store. Pi Bridge is an independent community project and is not affiliated with, sponsored by, or endorsed by Pi's maintainers or Google. Pi and the Pi logo remain the property of their respective owners.