pi-chrome 0.15.17 → 0.15.18

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/CHANGELOG.md +4 -0
  2. package/README.md +3 -3
  3. package/extensions/chrome-profile-bridge/browser-extension/manifest.json +1 -1
  4. package/package.json +2 -2
package/CHANGELOG.md CHANGED
@@ -2,6 +2,10 @@
2
2
 
3
3
  All notable user-facing changes to `pi-chrome`.
4
4
 
5
+ ## 0.15.18 — 2026-05-14
6
+
7
+ - **Cleaner package description.** npm/pi.dev description now focuses on the existing Chrome profile and explicit authorization model, avoiding implementation details.
8
+
5
9
  ## 0.15.17 — 2026-05-14
6
10
 
7
11
  - **Docs accuracy pass.** Updated README, FAQ, comparison, contributing notes, and package metadata for the current real-input-only, terminal-authorized tool surface.
package/README.md CHANGED
@@ -1,7 +1,7 @@
1
1
  # pi-chrome
2
2
 
3
- > **The fastest way to give a [Pi](https://pi.dev) agent your real Chrome.**
4
- > No remote-debug port. No throwaway profile. No re-login. Watch it work — or run silent.
3
+ > **Let a [Pi](https://pi.dev) agent use your existing signed-in Chrome profile.**
4
+ > Explicitly authorize each Pi session. No throwaway browser, no re-login.
5
5
 
6
6
  **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`.
7
7
 
@@ -12,7 +12,7 @@ Agent: chrome_tab(list) → chrome_snapshot(uid:…) → chrome_screenshot(...)
12
12
  You: [keeps coding — agent never asked you to log in]
13
13
  ```
14
14
 
15
- `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.
15
+ `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.
16
16
 
17
17
  ---
18
18
 
package/extensions/chrome-profile-bridge/browser-extension/manifest.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "manifest_version": 3,
3
3
  "name": "Pi Chrome Connector",
4
- "version": "0.15.17",
4
+ "version": "0.15.18",
5
5
  "description": "Lets Pi control tabs in Chrome via a local connector at 127.0.0.1.",
6
6
  "permissions": [
7
7
  "tabs",
package/package.json CHANGED
@@ -1,11 +1,11 @@
1
1
  {
2
2
  "name": "pi-chrome",
3
- "version": "0.15.17",
3
+ "version": "0.15.18",
4
4
  "scripts": {
5
5
  "version": "node scripts/sync-manifest-version.js",
6
6
  "prepublishOnly": "node scripts/sync-manifest-version.js"
7
7
  },
8
- "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.",
8
+ "description": "Let Pi use your existing signed-in Chrome profile after explicit authorization. No throwaway browser, no re-login.",
9
9
  "keywords": [
10
10
  "pi",
11
11
  "pi-package",