pi-chrome 0.15.11 → 0.15.13

package/CHANGELOG.md

@@ -2,6 +2,14 @@
 
 All notable user-facing changes to `pi-chrome`.
 
+## 0.15.13 — 2026-05-14
+
+- **Fix Chrome-side consent hang.** `/chrome authorize` now launches the browser consent page as a short command, then polls for the decision. This avoids holding one long extension command open while the user reads/clicks the page, which could leave Pi stuck at “Opening Chrome approval page…”.
+
+## 0.15.12 — 2026-05-14
+
+- **Docs accuracy.** Clarified that the bundled Chrome extension currently polls `127.0.0.1:17318`; custom bridge ports are not supported without editing/reloading the extension source. Also softened the unpacked-extension rationale to avoid overstating Web Store limitations and fixed stale strict-CSP guidance for `chrome_evaluate`.
+
 ## 0.15.11 — 2026-05-14
 
 - **README cleanup.** Removed the Playwright/CDP/Selenium comparison table and low-signal Composes with / Contributing sections from the package page because they are noisy and easy to drift.

package/README.md

@@ -237,17 +237,13 @@ If you build a competing tool, please open a PR with your scores. We benchmark i
 
 ## Security model & why unpacked
 
-**Unpacked on purpose.** A Web Store extension cannot talk to a local bridge controlled by another tool on the same machine — so pi-chrome ships its bridge as an inspectable, MIT-licensed folder you load once with Developer Mode. Every line is yours to read in [`extensions/chrome-profile-bridge/browser-extension/`](./extensions/chrome-profile-bridge/browser-extension). `/chrome doctor` reports the loaded extension version and warns when it drifts from your installed `pi-chrome`.
+**Unpacked on purpose.** pi-chrome ships as an inspectable, MIT-licensed extension folder you load once with Developer Mode, so the local bridge and browser permissions are easy to audit and update without a Web Store release cycle. Every line is yours to read in [`extensions/chrome-profile-bridge/browser-extension/`](./extensions/chrome-profile-bridge/browser-extension). `/chrome doctor` reports the loaded extension version and warns when it drifts from your installed `pi-chrome`.
 
 The companion extension runs in the Chrome profile where you install it and has broad tab/scripting permissions. Only install it from a package source you trust. Even after install, `chrome_*` tools stay locked until you run `/chrome authorize` in Pi and approve the browser-side consent page in Chrome. Use `/chrome revoke` to lock them again.
 
-The Pi side listens on `127.0.0.1:17318` by default and rejects browser-origin command requests; ordinary web pages cannot use CORS to drive the bridge. Override before starting Pi:
+The Pi side listens on `127.0.0.1:17318` and rejects browser-origin command requests; ordinary web pages cannot use CORS to drive the bridge. The bundled Chrome extension currently polls that default port, so custom bridge ports are not supported without editing the extension source and reloading it.
 
-```bash
-PI_CHROME_BRIDGE_PORT=17319 pi
-```
-
-There is no network exposure; the bridge binds to loopback only.
+There is no network exposure in the default configuration; the bridge binds to loopback only.
 
 ---
 

package/SECURITY.md

@@ -29,11 +29,9 @@ The Chrome extension under `extensions/chrome-profile-bridge/browser-extension/`
 - Chrome control locked by default; `/chrome authorize` opens a Chrome consent page, approval unlocks current Pi session, `/chrome revoke` locks it again.
 - Run-in-background optional; tab/window focus is observable by default (the user can see Pi acting).
 
-## Override the port
+## Custom ports
 
-```bash
-PI_CHROME_BRIDGE_PORT=17319 pi
-```
+The bundled Chrome extension currently polls `127.0.0.1:17318`. Custom bridge ports are not supported without editing the extension source and reloading it.
 
 ## Supported versions
 

package/docs/FAQ.md

@@ -51,7 +51,7 @@ The Pi-facing tools are thin wrappers around an HTTP bridge at `127.0.0.1:17318`
 
 ## Does `chrome_evaluate` work on strict-CSP pages?
 
-Yes. The handler compiles with `new Function(...)` in the MAIN world, which works under `script-src 'self'` without `'unsafe-eval'`. Multi-statement bodies are supported via a statement-mode fallback. Exceptions are surfaced to the agent.
+Not always. `chrome_evaluate` and `chrome_snapshot` run in the page's MAIN world through the Function constructor, so pages whose CSP blocks `'unsafe-eval'` can reject them. `chrome_screenshot`, `chrome_navigate`, tab tools, and real Chrome input still work because they use extension/browser APIs rather than page JavaScript.
 
 ## Why does my click return `pageMutated=false`?
 

package/extensions/chrome-profile-bridge/browser-extension/manifest.json

@@ -1,7 +1,7 @@
 {
   "manifest_version": 3,
   "name": "Pi Chrome Connector",
-  "version": "0.15.11",
+  "version": "0.15.13",
   "description": "Lets Pi control tabs in Chrome via a local connector at 127.0.0.1.",
   "permissions": [
     "tabs",

package/extensions/chrome-profile-bridge/browser-extension/service_worker.js

@@ -4,7 +4,8 @@ const POLL_ERROR_BACKOFF_MS = 2000;
 const CONSENT_TIMEOUT_MS = 5 * 60 * 1000;
 let polling = false;
 let nextConsentRequestId = 1;
-const pendingConsentRequests = new Map(); // id -> { request, resolve, timer, tabId }
+const pendingConsentRequests = new Map(); // id -> { request, timer, tabId }
+const completedConsentRequests = new Map(); // id -> { approved, reason, id, decidedAt }
 
 // =================== Chrome input (CDP) layer ===================
 // Tracks which tabs we have attached chrome.debugger to.
@@ -607,35 +608,45 @@ function consentRequestSnapshot(id, request) {
   };
 }
 
+function completeBrowserConsent(id, approved, reason, closeTab = true) {
+  const pending = pendingConsentRequests.get(id);
+  if (!pending) return completedConsentRequests.get(id) || null;
+  pendingConsentRequests.delete(id);
+  clearTimeout(pending.timer);
+  if (closeTab && pending.tabId) chrome.tabs.remove(pending.tabId).catch(() => undefined);
+  const result = { approved, reason, id, decidedAt: Date.now() };
+  completedConsentRequests.set(id, result);
+  setTimeout(() => completedConsentRequests.delete(id), 10 * 60 * 1000);
+  return result;
+}
+
 async function requestBrowserConsent(params) {
   const id = String(nextConsentRequestId++);
   const request = {
     ...params,
     requestedAt: Date.now(),
   };
+  const timer = setTimeout(() => completeBrowserConsent(id, false, "timed out waiting for browser approval"), CONSENT_TIMEOUT_MS);
+  pendingConsentRequests.set(id, { request, timer, tabId: null });
   const url = chrome.runtime.getURL(`consent.html?id=${encodeURIComponent(id)}`);
-  const decision = new Promise((resolve) => {
-    const finish = (approved, reason) => {
-      const pending = pendingConsentRequests.get(id);
-      if (!pending) return;
-      pendingConsentRequests.delete(id);
-      clearTimeout(pending.timer);
-      if (pending.tabId) chrome.tabs.remove(pending.tabId).catch(() => undefined);
-      resolve({ approved, reason, id, decidedAt: Date.now() });
-    };
-    const timer = setTimeout(() => finish(false, "timed out waiting for browser approval"), CONSENT_TIMEOUT_MS);
-    pendingConsentRequests.set(id, { request, resolve: finish, timer, tabId: null });
-  });
   try {
     const tab = await chrome.tabs.create({ url, active: true });
     if (tab.windowId !== undefined) await chrome.windows.update(tab.windowId, { focused: true }).catch(() => undefined);
     const pending = pendingConsentRequests.get(id);
     if (pending) pending.tabId = tab.id;
   } catch (error) {
-    const pending = pendingConsentRequests.get(id);
-    if (pending) pending.resolve(false, `could not open consent tab: ${error?.message || error}`);
+    completeBrowserConsent(id, false, `could not open consent tab: ${error?.message || error}`, false);
   }
-  return await decision;
+  return { id, opened: pendingConsentRequests.has(id), timeoutMs: CONSENT_TIMEOUT_MS };
+}
+
+function browserConsentStatus(params) {
+  const id = String(params?.id || "");
+  const completed = completedConsentRequests.get(id);
+  if (completed) return { state: "done", ...completed };
+  const pending = pendingConsentRequests.get(id);
+  if (pending) return { state: "pending", id, requestedAt: pending.request.requestedAt, timeoutMs: CONSENT_TIMEOUT_MS };
+  return { state: "missing", id, approved: false, reason: "consent request expired or not found" };
 }
 
 chrome.runtime.onMessage.addListener((message, sender, sendResponse) => {
@@ -648,12 +659,11 @@ chrome.runtime.onMessage.addListener((message, sender, sendResponse) => {
   }
   if (message.type === "piChromeConsentDecision") {
     const id = String(message.id || "");
-    const pending = pendingConsentRequests.get(id);
-    if (!pending) {
+    const result = completeBrowserConsent(id, message.approved === true, message.approved === true ? "approved in Chrome" : "denied in Chrome");
+    if (!result) {
       sendResponse({ ok: false, error: "Consent request expired or not found" });
       return true;
     }
-    pending.resolve(message.approved === true, message.approved === true ? "approved in Chrome" : "denied in Chrome");
     sendResponse({ ok: true });
     return true;
   }
@@ -662,11 +672,7 @@ chrome.runtime.onMessage.addListener((message, sender, sendResponse) => {
 
 chrome.tabs.onRemoved.addListener((tabId) => {
   for (const [id, pending] of pendingConsentRequests) {
-    if (pending.tabId === tabId) {
-      pending.resolve(false, "consent tab closed");
-      pendingConsentRequests.delete(id);
-      clearTimeout(pending.timer);
-    }
+    if (pending.tabId === tabId) completeBrowserConsent(id, false, "consent tab closed", false);
   }
 });
 
@@ -767,6 +773,8 @@ async function dispatch(action, params) {
       };
     case "consent.request":
       return requestBrowserConsent(params);
+    case "consent.status":
+      return browserConsentStatus(params);
     case "tab.list":
       return (await chrome.tabs.query({})).map(formatTab);
     case "tab.new": {

package/extensions/chrome-profile-bridge/index.ts

@@ -463,6 +463,8 @@ export default function (pi: ExtensionAPI): void {
 		return bridge.send(action, params, timeoutMs);
 	};
 
+	const sleep = (ms: number) => new Promise((resolveSleep) => setTimeout(resolveSleep, ms));
+
 	// Translate the public `background` parameter (default false = visible/foreground) into the
 	// service worker's wire-level `foreground` flag, accepting legacy `foreground` as a fallback.
 	const withBackground = <T extends Record<string, unknown>>(params: T): T => {
@@ -610,14 +612,14 @@ Usage rules:
 
 	const authorizeFor = async (ctx: ExtensionContext, label: string, until: number | "indefinite") => {
 		ctx.ui.notify("Opening Chrome approval page…", "info");
-		let consent: { approved?: boolean; reason?: string };
+		let request: { id?: string; opened?: boolean; timeoutMs?: number };
 		try {
-			consent = (await bridge.send("consent.request", {
+			request = (await bridge.send("consent.request", {
 				durationLabel: label,
 				workspace: workspaceCwd(ctx),
 				pid: process.pid,
 				piChromeVersion: PI_CHROME_VERSION,
-			}, 5 * 60_000 + 5_000)) as { approved?: boolean; reason?: string };
+			}, 10_000)) as { id?: string; opened?: boolean; timeoutMs?: number };
 		} catch (error) {
 			const message = (error as Error).message;
 			const hint = message.includes("Unknown action: consent.request")
@@ -626,12 +628,36 @@ Usage rules:
 			ctx.ui.notify(`Chrome approval failed: ${message}\n${hint}`, "warning");
 			return;
 		}
-		if (!consent.approved) {
-			ctx.ui.notify(`Chrome control remains locked${consent.reason ? ` (${consent.reason})` : ""}.`, "info");
+		if (!request.id) {
+			ctx.ui.notify("Chrome approval failed: companion extension did not return a consent request id.", "warning");
+			return;
+		}
+		if (!request.opened) {
+			ctx.ui.notify("Chrome approval failed: companion extension could not open the consent page.", "warning");
 			return;
 		}
-		chromeAuthorizedUntil = until;
-		ctx.ui.notify(`Chrome control authorized for ${label}.`, "info");
+
+		const deadline = Date.now() + (request.timeoutMs ?? 5 * 60_000);
+		while (Date.now() < deadline + 2_000) {
+			await sleep(700);
+			let status: { state?: string; approved?: boolean; reason?: string };
+			try {
+				status = (await bridge.send("consent.status", { id: request.id }, 5_000)) as { state?: string; approved?: boolean; reason?: string };
+			} catch (error) {
+				ctx.ui.notify(`Chrome approval failed: ${(error as Error).message}`, "warning");
+				return;
+			}
+			if (status.state !== "pending") {
+				if (!status.approved) {
+					ctx.ui.notify(`Chrome control remains locked${status.reason ? ` (${status.reason})` : ""}.`, "info");
+					return;
+				}
+				chromeAuthorizedUntil = until;
+				ctx.ui.notify(`Chrome control authorized for ${label}.`, "info");
+				return;
+			}
+		}
+		ctx.ui.notify("Chrome control remains locked (timed out waiting for browser approval).", "info");
 	};
 
 	const parseAuthorizeArg = (arg: string): { label: string; until: number | "indefinite" } | undefined => {
@@ -835,7 +861,7 @@ Usage rules:
 			"Start/check the local bridge used by the companion Chrome extension. This does not launch a separate Chrome profile; install the unpacked Chrome extension in your existing Chrome profile to connect.",
 		promptSnippet: "Show instructions for connecting Pi to the user's existing Chrome profile via the companion extension.",
 		parameters: Type.Object({
-			port: Type.Optional(Type.Number({ description: "Ignored unless PI_CHROME_BRIDGE_PORT is set before Pi starts." })),
+			port: Type.Optional(Type.Number({ description: "Ignored. The bundled Chrome extension polls 127.0.0.1:17318." })),
 			url: Type.Optional(Type.String({ description: "Optional URL to open in the existing Chrome profile after the extension is connected." })),
 			userDataDir: Type.Optional(Type.String({ description: "Ignored. This bridge intentionally uses the user's existing Chrome profile through the companion extension." })),
 			useDefaultProfile: Type.Optional(Type.Boolean({ description: "Ignored; existing-profile access comes from the companion Chrome extension." })),

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "pi-chrome",
-	"version": "0.15.11",
+	"version": "0.15.13",
 	"scripts": {
 		"version": "node scripts/sync-manifest-version.js",
 		"prepublishOnly": "node scripts/sync-manifest-version.js"