pi-browser-use 0.3.2 → 0.3.3
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/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "pi-browser-use",
|
|
3
|
-
"version": "0.3.
|
|
3
|
+
"version": "0.3.3",
|
|
4
4
|
"description": "Opinionated browser-use for the Pi coding agent, powered by chrome-devtools-mcp (not Playwright). Fresh headless by default, authenticated persistent profile opt-in, CLI-first policy bundled.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"pi-package",
|
|
@@ -69,6 +69,10 @@ PLAYWRIGHT_HEADLESS=1 bunx playwright test --config=playwright.config.ts
|
|
|
69
69
|
|
|
70
70
|
Keep headed runs for human-watched perf validation only.
|
|
71
71
|
|
|
72
|
+
## Python alternative
|
|
73
|
+
|
|
74
|
+
For Python-first repos, the global `webapp-testing` skill covers the same ground with `sync_playwright()` scripts and a multi-server lifecycle helper — same handoff rule applies regardless of language.
|
|
75
|
+
|
|
72
76
|
## Reporting back
|
|
73
77
|
|
|
74
78
|
Summarize pass/fail plus the failing assertion or trace path. Delete nothing from the repo — the only artifacts are `/tmp/*.spec.ts` and the shared browser cache.
|
|
@@ -22,7 +22,7 @@ Save, don't inline — `browser_save_artifact` returns paths. Inline `browser_ta
|
|
|
22
22
|
|
|
23
23
|
## When the tree is blind (canvas/WebGL)
|
|
24
24
|
|
|
25
|
-
1. `browser_analyze_screenshot` (requires `visionModel` config) for coordinates or element identification the tree cannot provide.
|
|
25
|
+
1. `browser_analyze_screenshot` (requires `visionModel` config) for coordinates or element identification the tree cannot provide. Without it and with a vision-less model, fall back to the global `vision` skill (external Gemini describe script) instead of guessing pixels.
|
|
26
26
|
2. Feed coordinates to `browser_click_at` — never guess pixels yourself.
|
|
27
27
|
3. If the scene needs deterministic frames (animations, thumbnails), stop: that is `playwright-handoff` territory (`waitForFunction`, fixed timeouts, traces).
|
|
28
28
|
|