crewx-pi-kit 0.1.10 → 0.1.11

package/README.md

@@ -10,7 +10,7 @@ work, safety boundaries, and agent handoffs.
 Install it with Pi:
 
 ```sh
-pi install npm:crewx-pi-kit@0.1.10
+pi install npm:crewx-pi-kit@0.1.11
 ```
 
 CrewX injects short-lived `CREWX_URL` and `CREWX_TOKEN` capabilities only while

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "crewx-pi-kit",
-  "version": "0.1.10",
+  "version": "0.1.11",
   "description": "Typed CrewX tools and operating skills for managed Pi agents.",
   "type": "module",
   "files": [

package/skills/browser-work/SKILL.md

@@ -12,7 +12,7 @@ Cua calls can be safely grouped.
 
 1. Reuse the managed persistent browser profile and existing pages. Do not launch throwaway profiles unless isolation is required.
 2. Start by listing windows, then bind browser work to the exact browser PID and window ID returned by that snapshot. Reuse one short session label for every related Cua browser call.
-3. If binding returns `browser_consent_required` for the managed persistent profile, call `browser_prepare` on the same MCP connection with that exact `pid`, `window_id`, and `strategy: { "kind": "existing_profile" }`. Then bind the window again. Do not omit the strategy merely because the DevTools endpoint is already available; endpoint readiness and profile authorization are separate.
+3. If binding returns `browser_consent_required` for the managed persistent profile, call `browser_prepare` on the same MCP connection with that exact `pid`, `window_id`, `strategy: { "kind": "existing_profile" }`, and the identical `session` value used for the bind. Then bind the window again with that same session. Mixing an unnamed prepare with a named bind loses the session-scoped authorization. Do not omit the strategy merely because the DevTools endpoint is already available; endpoint readiness and profile authorization are separate.
 4. Prefer semantic accessibility targets. When a trusted click is refused on Linux, use the explicit DOM-event fallback and verify the resulting page state.
 5. Use coordinates only when no stable semantic target exists.
 6. Inspect the current URL and page state before acting. Re-snapshot after navigation or state changes; never infer success from a click alone.