pi-chrome 0.15.1 → 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.
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.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
|
+
|
|
5
9
|
## 0.15.1 — 2026-05-13
|
|
6
10
|
|
|
7
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.
|
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
|
-
|
|
56
|
-
|
|
57
|
-
|
|
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: "
|
|
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
|
|
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: "
|
|
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
|
|
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,
|
|
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,
|
|
120
|
+
> Open the photo uploader, upload `./fixtures/sample.png`, confirm the preview renders.
|
|
122
121
|
|
|
123
122
|
</details>
|
|
124
123
|
|