pi-chrome 0.1.0 → 0.1.1
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/README.md +32 -4
- package/package.json +6 -3
package/README.md
CHANGED
|
@@ -1,8 +1,14 @@
|
|
|
1
1
|
# pi-chrome
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
Control the Chrome profile you already use from Pi.
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
`pi-chrome` gives Pi agents browser tools for your **real Chrome windows, tabs, and authenticated sessions**. It uses a companion Chrome extension instead of the Chrome DevTools Protocol (CDP), so it does not launch a throwaway debug browser profile and does not require re-signing into the apps you already have open.
|
|
6
|
+
|
|
7
|
+
## Why try it?
|
|
8
|
+
|
|
9
|
+
- **Uses your existing Chrome profile** — works with the Chrome windows/tabs you are already using, including logged-in GitHub, admin dashboards, local apps, and internal tools.
|
|
10
|
+
- **Full browser automation toolkit for Pi** — list/create/activate/close tabs, snapshot pages with usable CSS selectors, navigate, evaluate JavaScript, click, type, press keys, wait for page state, and capture screenshots.
|
|
11
|
+
- **Built-in setup and agent guidance** — `/chrome-onboard` walks users through installing the companion extension, `/chrome-status` checks connectivity, screenshots save to disk, and the prompt primer tells agents to inspect with `chrome_snapshot` before acting and avoid destructive actions unless explicitly requested.
|
|
6
12
|
|
|
7
13
|
## Install
|
|
8
14
|
|
|
@@ -10,7 +16,7 @@ Unlike Chrome DevTools Protocol integrations, `pi-chrome` does not launch a sepa
|
|
|
10
16
|
pi install npm:pi-chrome
|
|
11
17
|
```
|
|
12
18
|
|
|
13
|
-
For local development from
|
|
19
|
+
For local development from a checkout:
|
|
14
20
|
|
|
15
21
|
```bash
|
|
16
22
|
pi install ./pi-chrome
|
|
@@ -24,7 +30,7 @@ In Pi, run:
|
|
|
24
30
|
/chrome-onboard
|
|
25
31
|
```
|
|
26
32
|
|
|
27
|
-
Pi
|
|
33
|
+
Pi first shows setup instructions and waits for confirmation. Press Enter to continue. On macOS it will:
|
|
28
34
|
|
|
29
35
|
- open `chrome://extensions`
|
|
30
36
|
- reveal the bundled `browser-extension` folder in Finder
|
|
@@ -48,6 +54,20 @@ Performing Chrome bridge health check
|
|
|
48
54
|
Chrome profile bridge connected (ID: <chrome-extension-id>)
|
|
49
55
|
```
|
|
50
56
|
|
|
57
|
+
## Quick demo prompt
|
|
58
|
+
|
|
59
|
+
After setup, try this in Pi:
|
|
60
|
+
|
|
61
|
+
```text
|
|
62
|
+
Use chrome_tab list to find my existing GitHub tab, chrome_snapshot it, then summarize the visible PR state. Do not click anything yet.
|
|
63
|
+
```
|
|
64
|
+
|
|
65
|
+
Or for a local web app repro:
|
|
66
|
+
|
|
67
|
+
```text
|
|
68
|
+
Use chrome_tab list to find my localhost app, inspect it with chrome_snapshot, navigate through the bug repro flow, and save a screenshot when you reach the broken state.
|
|
69
|
+
```
|
|
70
|
+
|
|
51
71
|
## Tools
|
|
52
72
|
|
|
53
73
|
The package registers these Pi tools:
|
|
@@ -63,6 +83,14 @@ The package registers these Pi tools:
|
|
|
63
83
|
- `chrome_wait_for` — wait for a selector or expression
|
|
64
84
|
- `chrome_screenshot` — capture viewport screenshots to disk
|
|
65
85
|
|
|
86
|
+
These tools are especially useful for authenticated web app debugging, repro flows, admin workflows, visual checks, and inspecting local development pages without rebuilding login state.
|
|
87
|
+
|
|
88
|
+
## How it works
|
|
89
|
+
|
|
90
|
+
Pi starts a local bridge on `127.0.0.1:17318`. The companion Chrome extension, installed in your normal Chrome profile, polls that local bridge for commands and executes them using Chrome extension APIs.
|
|
91
|
+
|
|
92
|
+
This is intentionally different from CDP-based tools: the browser extension lives inside the profile you already use, so Pi can interact with existing tabs and authenticated page state.
|
|
93
|
+
|
|
66
94
|
## Security model
|
|
67
95
|
|
|
68
96
|
The companion Chrome extension runs in the Chrome profile where you install it and has broad tab/scripting permissions. Only install it from a package source you trust.
|
package/package.json
CHANGED
|
@@ -1,13 +1,16 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "pi-chrome",
|
|
3
|
-
"version": "0.1.
|
|
4
|
-
"description": "
|
|
3
|
+
"version": "0.1.1",
|
|
4
|
+
"description": "Control your existing authenticated Chrome profile from Pi with tabs, snapshots, clicks, typing, JS evaluation, waits, and screenshots.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"pi-package",
|
|
7
7
|
"pi-extension",
|
|
8
8
|
"chrome",
|
|
9
9
|
"browser",
|
|
10
|
-
"automation"
|
|
10
|
+
"automation",
|
|
11
|
+
"authenticated-session",
|
|
12
|
+
"real-profile",
|
|
13
|
+
"web-debugging"
|
|
11
14
|
],
|
|
12
15
|
"license": "MIT",
|
|
13
16
|
"type": "commonjs",
|