pi-chrome 0.15.36 → 0.15.37

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
@@ -4,7 +4,7 @@ All notable user-facing changes to `pi-chrome`.
4
4
 
5
5
  ## 0.15.36 — 2026-06-03
6
6
 
7
- - **Richer page observation (ported from the `foxfirecodes` fork).** `chrome_snapshot` now returns a concise, agent-friendly observation — structural layout/context, page hints, visible actions, form fields, a page map, query matches, and a diff of changes since the previous snapshot — instead of a raw JSON dump. New `mode` (`auto`/`interactive`/`forms`/`pageMap`/`text`/`changes`/`full`), `query`, and `maxTextChars` parameters let the agent zoom in instead of dumping the whole page.
7
+ - **Richer page observation.** `chrome_snapshot` now returns a concise, agent-friendly observation — structural layout/context, page hints, visible actions, form fields, a page map, query matches, and a diff of changes since the previous snapshot — instead of a raw JSON dump. New `mode` (`auto`/`interactive`/`forms`/`pageMap`/`text`/`changes`/`full`), `query`, and `maxTextChars` parameters let the agent zoom in instead of dumping the whole page.
8
8
  - **New `chrome_find` tool.** Find elements, regions, or text by natural-language query (`'merge button'`, `'email error'`) and get ranked matches with stable uids and coordinates. Thin wrapper around `chrome_snapshot({ query })`.
9
9
  - **New `chrome_inspect` tool.** Inspect one snapshot uid/selector deeply: nearby text, nearby actions, form context, ancestors, and a suggested click target. Falls back to a focused snapshot if the loaded extension predates `page.inspect`.
10
10
  - **`includeSnapshot` now embeds the formatted snapshot.** `chrome_click`/`chrome_type`/`chrome_fill`/`chrome_key` with `includeSnapshot=true` append the fresh concise snapshot to the tool text so the agent can verify in one round trip.
package/README.md CHANGED
@@ -15,34 +15,58 @@ You: [keeps coding — agent never asked you to log in]
15
15
 
16
16
  ---
17
17
 
18
- ## 60-second install
18
+ ## 60-second install instruction
19
+
20
+ To install pi-chrome, run the following command:
19
21
 
20
22
  ```bash
21
23
  pi install npm:pi-chrome
22
24
  ```
23
25
 
24
- Then in Pi:
26
+
27
+ Then in Pi, run the next command, which will:
28
+
29
+ 1. Reveal the bundled browser-extension folder in Finder, and copy the folder path to your clipboard.
30
+ 2. Pop open the chrome://extensions webpage in Chrome.
31
+
32
+ In the Chrome Extensions page it opened, **YOU WILL NEED TO**:
33
+
34
+ 1. Turn on **developer mode** (top right).
35
+ 2. Click the **load unpacked** button (top left).
36
+ 3. Use **Cmd + Shift + G** (Mac) or **Ctrl + L** (Windows/Linux) to open the folder path field.
37
+ 4. **Cmd + V** (Mac) or **Ctrl + V** (Windows/Linux) to paste the copied path and press Enter.
38
+ 5. You're done with the chrome extensions page, and you can continue with the rest of the installation commands
25
39
 
26
40
  ```text
27
41
  /chrome onboard
28
42
  ```
29
43
 
30
- On macOS this opens `chrome://extensions`, reveals the bundled `browser-extension/` folder in Finder, and copies its path to your clipboard. In Chrome: **Developer mode** → **Load unpacked** → paste the path. Done.
44
+ Reload Pi so the newly installed package is actually loaded:
45
+
46
+ ```text
47
+ /reload
48
+ ```
49
+
31
50
 
32
- Verify, then authorize current Pi session from the terminal:
51
+ Verify the chrome connection:
33
52
 
34
53
  ```text
35
54
  /chrome doctor
36
- /chrome authorize
37
55
  ```
56
+ In the output, you just need to make sure the following line is present (It's okay if the other ones are still not checked):
57
+
58
+ ✓ Chrome is connected (companion extension v0.15.36, responded in 11ms).
38
59
 
60
+ Lastly, authorize the current session by running:
39
61
  ```text
40
- Performing Chrome bridge health check
41
- pi-chrome v<version>
42
- • Local bridge: mode=server, url=http://127.0.0.1:17318
43
- ✓ Companion Chrome extension responding (ID: <chrome-extension-id>, ext v<version>)
62
+ /chrome authorize
44
63
  ```
45
64
 
65
+ Run the following once more, and you should see all the lines checked:
66
+
67
+ ```text
68
+ /chrome doctor
69
+ ```
46
70
  ---
47
71
 
48
72
  ## Try this in 30 seconds after install
@@ -135,7 +159,7 @@ Agents can verify page state immediately instead of blindly retrying.
135
159
 
136
160
  ## What an agent gets
137
161
 
138
- **19 tools**, grouped by job. Every one runs against your already-open tabs.
162
+ **21 tools**, grouped by job. Every one runs against your already-open tabs.
139
163
 
140
164
  | Category | Tools |
141
165
  | --------------- | ---------------------------------------------------------------------------------------------- |
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "manifest_version": 3,
3
3
  "name": "Pi Chrome Connector",
4
- "version": "0.15.36",
4
+ "version": "0.15.37",
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,6 +1,6 @@
1
1
  {
2
2
  "name": "pi-chrome",
3
- "version": "0.15.36",
3
+ "version": "0.15.37",
4
4
  "scripts": {
5
5
  "test": "node test-suite/unit/csp-eval.test.mjs",
6
6
  "version": "node scripts/sync-manifest-version.js",