pi-chrome 0.15.0 → 0.15.2

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 +9 -0
  2. package/README.md +19 -20
  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,15 @@
2
2
 
3
3
  All notable user-facing changes to `pi-chrome`.
4
4
 
5
+ ## 0.15.2 — 2026-05-13
6
+
7
+ - **Recipe prompts rewritten in user-language.** Earlier recipes leaked tool names into the `You:` prompts ("Use `chrome_tab list` to find my GitHub notifications tab…"), implying users need to know the tool catalog before they can ask anything. Prompts now read as natural intent; the agent trace below each one still shows the `chrome_*` primitives the agent picked. Affects the 30-second try-this block, all 3 hero recipes (PR triage / Linear standup / Bug repro), and 3 of the 6 collapsed recipes (auth-only data pull, network forensics, file upload).
8
+
9
+ ## 0.15.1 — 2026-05-13
10
+
11
+ - **Architecture diagram now renders on pi.dev.** Replaced Unicode box-drawing characters (`┌─┐│└┘┬▼`) with plain ASCII (`+ - | v`). Pi.dev's monospace font was dropping the horizontal `─` glyphs, leaving the diagram as floating vertical bars. ASCII renders everywhere.
12
+ - **`author` switched to object form.** Was `"tianrendong (Earendil Inc.)"` — npm's author-string spec parses `(parens)` as the URL slot, so `"Earendil Inc."` ended up in `author.url`. Now `{ "name": "tianrendong", "company": "Earendil Inc." }`.
13
+
5
14
  ## 0.15.0 — 2026-05-13
6
15
 
7
16
  - **README rewrite — top-3 recipes as terminal mockups.** PR triage, Linear standup, and Bug-repro-with-evidence each get a copy-pasteable prompt → tool trace → result block modeled on the hero example. The other six recipes (form auto-fill, admin cross-check, visual diff, auth-only data pull, network forensics, file upload) collapsed into a `<details>` block so the section sells before it catalogs.
package/README.md CHANGED
@@ -52,10 +52,9 @@ pi-chrome v<version>
52
52
  ## Try this in 30 seconds after install
53
53
 
54
54
  ```text
55
- Use chrome_tab list to find my GitHub notifications tab.
56
- chrome_snapshot it, then write a 5-bullet triage:
57
- which PRs need my review today, sorted by staleness.
58
- Do not click anything yet.
55
+ Look at my GitHub notifications tab and triage which PRs
56
+ need my review today, sorted by staleness.
57
+ Don't click anything yet — just read and summarize.
59
58
  ```
60
59
 
61
60
  You'll watch the agent jump to your GitHub tab and read the page — using **your** session, **your** filters, **your** orgs.
@@ -69,7 +68,7 @@ Each recipe assumes the relevant tab is already open in the Chrome you control.
69
68
  **PR triage**
70
69
 
71
70
  ```text
72
- You: "Use chrome_tab list to find my GitHub notifications tab, then summarize PRs needing my review today, sorted by staleness."
71
+ You: "Look at my GitHub notifications tab and summarize the PRs needing my review today, sorted by staleness."
73
72
  Agent: chrome_tab(list) → chrome_snapshot(uid:el-notifications) → chrome_evaluate(...)
74
73
  ✓ 7 PRs waiting on you. 2 stale >3d (storage-rewrite, billing-v2).
75
74
  1 just turned CI-green (api-keys-prune). Full sorted list below.
@@ -79,7 +78,7 @@ You: [pastes the list straight into Linear]
79
78
  **Linear standup**
80
79
 
81
80
  ```text
82
- You: "Open my Linear current cycle in the active tab and write a 5-bullet standup."
81
+ You: "Open my Linear current cycle and write a 5-bullet standup from it."
83
82
  Agent: chrome_tab(activate, urlIncludes:"linear.app") → chrome_snapshot(uid:el-cycle) → chrome_evaluate(...)
84
83
  ✓ 5 in-progress, 2 blocked. Standup draft:
85
84
  • Shipped: bridge auto-recover. • In flight: trusted-mode retry path.
@@ -91,7 +90,7 @@ You: [drops it into #standup]
91
90
  **Bug repro with evidence**
92
91
 
93
92
  ```text
94
- You: "Repro the checkout 500 on staging, save a screenshot at each step under ./repro/."
93
+ You: "Reproduce the checkout 500 on staging. Save a screenshot at each step under ./repro/."
95
94
  Agent: chrome_navigate(staging) → chrome_click(uid:el-add-to-cart) → chrome_screenshot(./repro/01-cart.png)
96
95
  → chrome_click(uid:el-checkout) → chrome_list_network_requests() → chrome_screenshot(./repro/02-500.png)
97
96
  ✓ POST /api/checkout → 500. Response body saved → ./repro/checkout-500.json
@@ -112,13 +111,13 @@ You: [files the ticket with the folder attached]
112
111
  > Snapshot `localhost:3000` and the staging URL of the same page; tell me what's visually different.
113
112
 
114
113
  **Auth-only data pull**
115
- > Open my analytics dashboard tab and `chrome_evaluate` to extract today's KPIs from page state.
114
+ > Open my analytics dashboard tab and pull today's KPIs from the page.
116
115
 
117
116
  **Network forensics**
118
- > Reproduce the checkout bug, then use `chrome_list_network_requests` to find the failing call and dump its response body.
117
+ > Reproduce the checkout bug, find the failing API call, and dump its response body.
119
118
 
120
119
  **File upload through React**
121
- > Open the photo uploader, `chrome_upload_file` with `./fixtures/sample.png`, confirm preview rendered.
120
+ > Open the photo uploader, upload `./fixtures/sample.png`, confirm the preview renders.
122
121
 
123
122
  </details>
124
123
 
@@ -222,16 +221,16 @@ If the loaded Chrome extension is older than `pi-chrome` on disk, `/chrome docto
222
221
 
223
222
  ## Architecture
224
223
 
225
- ```
226
- ┌──────────────────────┐ ┌──────────────────────────┐
227
- │ Pi agent (terminal) │ ─── http://127.0.0.1:17318 ─→ │ Chrome extension │
228
- │ chrome_* tools │ │ (your real profile) │
229
- └──────────┬───────────┘ └─────────┬────────────────┘
230
- │ same machine │
231
- ▼ ▼
232
- Other Pi sessions Tabs you already have open
233
- share the same bridge (signed in to GitHub,
234
- automatically Linear, Stripe, etc.)
224
+ ```text
225
+ +----------------------+ +--------------------------+
226
+ | Pi agent (terminal) | -- 127.0.0.1:17318 ->| Chrome extension |
227
+ | chrome_* tools | | (your real profile) |
228
+ +-----------+----------+ +-------------+------------+
229
+ | same machine |
230
+ v v
231
+ Other Pi sessions Tabs you already have open
232
+ share the same bridge (signed in to GitHub,
233
+ automatically Linear, Stripe, etc.)
235
234
  ```
236
235
 
237
236
  Multiple Pi sessions (planner / worker / audit) can all drive the same Chrome at once. The first session opens the local bridge; later sessions detect it and pipe their commands through.
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.0",
4
+ "version": "0.15.2",
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.0",
3
+ "version": "0.15.2",
4
4
  "scripts": {
5
5
  "version": "node scripts/sync-manifest-version.js",
6
6
  "prepublishOnly": "node scripts/sync-manifest-version.js"
@@ -36,7 +36,7 @@
36
36
  "stagehand-alternative"
37
37
  ],
38
38
  "license": "MIT",
39
- "author": "tianrendong (Earendil Inc.)",
39
+ "author": { "name": "tianrendong", "company": "Earendil Inc." },
40
40
  "homepage": "https://github.com/tianrendong/pi-chrome#readme",
41
41
  "repository": {
42
42
  "type": "git",