all repos — sz-chrome-remote-extension @ a356e410197a83954dbd4f70b6999a2ffac75b62

pi-chrome, patched to drive a signed-in browser on another host through a broker, with an MCP server

Refine package description
Tianren Dong tianrendong.dtr@gmail.com
Thu, 14 May 2026 22:49:09 -0400
commit

a356e410197a83954dbd4f70b6999a2ffac75b62

parent

58e86b70a0c7f6bf8e44f8b658e8194444ade943

M CHANGELOG.md → CHANGELOG.md

@@ -2,6 +2,10 @@ # Changelog

All notable user-facing changes to `pi-chrome`. +## 0.15.18 — 2026-05-14 + +- **Cleaner package description.** npm/pi.dev description now focuses on the existing Chrome profile and explicit authorization model, avoiding implementation details. + ## 0.15.17 — 2026-05-14 - **Docs accuracy pass.** Updated README, FAQ, comparison, contributing notes, and package metadata for the current real-input-only, terminal-authorized tool surface.
M README.md → README.md

@@ -1,7 +1,7 @@

# pi-chrome -> **The fastest way to give a [Pi](https://pi.dev) agent your real Chrome.** -> No remote-debug port. No throwaway profile. No re-login. Watch it work — or run silent. +> **Let a [Pi](https://pi.dev) agent use your existing signed-in Chrome profile.** +> Explicitly authorize each Pi session. No throwaway browser, no re-login. **MIT · 0 runtime deps · loopback-only bridge (`127.0.0.1:17318`) · inspect [`extensions/chrome-profile-bridge/browser-extension/`](./extensions/chrome-profile-bridge/browser-extension) before loading.** Verify connectivity in one command: `/chrome doctor`.

@@ -12,7 +12,7 @@ ✓ 3 reviewers, 1 change requested, CI red on iOS. Saved → .pi/chrome-screenshots/ci.png

You: [keeps coding — agent never asked you to log in] ``` -`pi-chrome` ships **19 browser tools** for Pi agents, backed by a small MIT-licensed Chrome extension that runs inside the Chrome profile **you already use** — including every site you're already signed into. +`pi-chrome` is backed by a small MIT-licensed Chrome extension that runs inside the Chrome profile **you already use** — including every site you're already signed into. Agents can inspect or control Chrome only after you run `/chrome authorize` in the current Pi session. ---
M extensions/chrome-profile-bridge/browser-extension/manifest.json → extensions/chrome-profile-bridge/browser-extension/manifest.json

@@ -1,7 +1,7 @@

{ "manifest_version": 3, "name": "Pi Chrome Connector", - "version": "0.15.17", + "version": "0.15.18", "description": "Lets Pi control tabs in Chrome via a local connector at 127.0.0.1.", "permissions": [ "tabs",
M package.json → package.json

@@ -1,11 +1,11 @@

{ "name": "pi-chrome", - "version": "0.15.17", + "version": "0.15.18", "scripts": { "version": "node scripts/sync-manifest-version.js", "prepublishOnly": "node scripts/sync-manifest-version.js" }, - "description": "Give a Pi agent your real, signed-in Chrome. No remote-debug port, no throwaway profile, no re-login. 19 tools for click, type, navigate, screenshot, network capture, file upload, drag, and touch.", + "description": "Let Pi use your existing signed-in Chrome profile after explicit authorization. No throwaway browser, no re-login.", "keywords": [ "pi", "pi-package",