pi-chrome 0.15.10 → 0.15.11
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.
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.11 — 2026-05-14
|
|
6
|
+
|
|
7
|
+
- **README cleanup.** Removed the Playwright/CDP/Selenium comparison table and low-signal Composes with / Contributing sections from the package page because they are noisy and easy to drift.
|
|
8
|
+
|
|
5
9
|
## 0.15.10 — 2026-05-14
|
|
6
10
|
|
|
7
11
|
- **Browser-side Chrome consent.** `/chrome authorize` now opens a Pi Chrome Connector approval page inside Chrome showing duration, workspace, process id, and extension/package versions. Chrome control unlocks only after the user approves there; denying, closing the tab, or timeout leaves control locked.
|
package/README.md
CHANGED
|
@@ -120,28 +120,6 @@ You: [files the ticket with the folder attached]
|
|
|
120
120
|
|
|
121
121
|
---
|
|
122
122
|
|
|
123
|
-
## Why pi-chrome vs. Playwright / CDP / Selenium
|
|
124
|
-
|
|
125
|
-
> Short version: **pi-chrome is primitives — "Playwright for the Chrome you're already signed into."** Not an agent loop. Plug it under any agent framework (Browser Use, Stagehand, LangGraph) or call its tools directly from a Pi agent. See [docs/COMPARISON.md](./docs/COMPARISON.md) for the full three-axis landscape (drivers, agents, cloud providers).
|
|
126
|
-
|
|
127
|
-
| | **pi-chrome** | Playwright / Puppeteer | CDP-based agents | Selenium / WebDriver |
|
|
128
|
-
| ------------------------------ | --------------------------------- | ----------------------------- | ----------------------------- | ----------------------------- |
|
|
129
|
-
| **Time from `pi install` → first useful action on your real account** | ~60s (load unpacked, `/chrome doctor`) | hours (script login, store creds, debug headless) | 30+ min (`--remote-debug` setup, attach) | hours (driver + login script) |
|
|
130
|
-
| **Survives MFA / SSO without code** | ✅ already logged in | ❌ | ⚠️ if you re-auth | ❌ |
|
|
131
|
-
| Uses your real signed-in Chrome | ✅ extension in your profile | ❌ throwaway profile | ⚠️ requires `--remote-debug` | ❌ throwaway profile |
|
|
132
|
-
| Re-login required | **Never** | Every run | Sometimes | Every run |
|
|
133
|
-
| **Multiple agents drive the same Chrome at once** | ✅ shared bridge | ❌ port collisions | ❌ | ❌ |
|
|
134
|
-
| Watch agent work, live | ✅ default; run in background optional | ❌ headless or new window | ⚠️ debugger banner always | ❌ new window |
|
|
135
|
-
| Real browser input | ✅ always for input tools | ✅ | ✅ | ✅ |
|
|
136
|
-
| Network/console capture | ✅ built-in | ✅ | ✅ | ⚠️ via extensions |
|
|
137
|
-
| **Honest result envelopes¹** | ✅ | ⚠️ | ❌ | ❌ |
|
|
138
|
-
| Self-graded by built-in benchmark² | ✅ 38 primitives + 4 long-horizon | n/a | n/a | n/a |
|
|
139
|
-
|
|
140
|
-
¹ Every action returns `pageMutated`, `defaultPrevented`, `elementVisible`, `occludedBy`, and `valueMatches` so the agent knows when a click didn't take effect — instead of looping blindly.
|
|
141
|
-
² [`test-suite/`](./test-suite) grades browser-control primitives across input fidelity, activation gates, DOM complexity, and agent safety. If you build a competing tool, send a PR with your scores. We benchmark in public.
|
|
142
|
-
|
|
143
|
-
---
|
|
144
|
-
|
|
145
123
|
## Honest results
|
|
146
124
|
|
|
147
125
|
Most browser-automation libraries return `void` or a generic ack. `pi-chrome` returns a structured envelope on every interaction:
|
|
@@ -273,14 +251,6 @@ There is no network exposure; the bridge binds to loopback only.
|
|
|
273
251
|
|
|
274
252
|
---
|
|
275
253
|
|
|
276
|
-
## Composes with
|
|
277
|
-
|
|
278
|
-
- **[pi-qq](https://www.npmjs.com/package/pi-qq)** — `/qq summarize what the active GitHub tab shows` without polluting the main transcript.
|
|
279
|
-
- **[pi-bar](https://www.npmjs.com/package/pi-bar)** — when the agent scrapes large pages, watch the context-usage segment turn yellow → red as a signal to `/qq` for a recap.
|
|
280
|
-
- **PR demo skills** — screenshots write to `.pi/chrome-screenshots/` so you can attach them to PR descriptions or demo bundles.
|
|
281
|
-
|
|
282
|
-
---
|
|
283
|
-
|
|
284
254
|
## Roadmap signals
|
|
285
255
|
|
|
286
256
|
`pi-chrome` is actively shipped. Things on the near roadmap:
|
|
@@ -294,16 +264,6 @@ If you want one of those next, open an issue.
|
|
|
294
264
|
|
|
295
265
|
---
|
|
296
266
|
|
|
297
|
-
## Contributing
|
|
298
|
-
|
|
299
|
-
PRs welcome. The bar:
|
|
300
|
-
|
|
301
|
-
1. Add a benchmark page in `test-suite/` that fails before your change and passes after.
|
|
302
|
-
2. Keep `chrome_*` tool results honest — surface `pageMutated`, `valueMatches`, `defaultPrevented`, etc.
|
|
303
|
-
3. Don't break the "no re-login" guarantee. Anything that requires a fresh profile is out of scope.
|
|
304
|
-
|
|
305
|
-
---
|
|
306
|
-
|
|
307
267
|
## License
|
|
308
268
|
|
|
309
269
|
MIT. See [LICENSE](./LICENSE).
|