pi-chrome 0.4.3 → 0.5.0

package/README.md

@@ -13,7 +13,7 @@ Multiple Pi sessions can use Chrome at the same time. The first Pi session start
 - **Uses your existing Chrome profile** — works with the Chrome windows/tabs you are already using, including logged-in GitHub, admin dashboards, local apps, and internal tools.
 - **Background by default** — agents can inspect, navigate, click, type, and snapshot without bringing Chrome to the foreground or interrupting whatever you are doing. Toggle for the whole session with `/chrome-foreground`, or pass `foreground: true` on a single tool call.
 - **Full browser automation toolkit for Pi** — list/create/activate/close tabs, snapshot pages with usable CSS selectors, navigate, evaluate JavaScript, click, type, press keys, wait for page state, and capture screenshots.
-- **Built-in setup and agent guidance** — `/chrome-onboard` walks users through installing the companion extension, `/chrome-status` checks connectivity, screenshots save to disk, and the prompt primer tells agents to inspect with `chrome_snapshot` before acting and avoid destructive actions unless explicitly requested.
+- **Built-in setup and agent guidance** — `/chrome-onboard` walks users through installing the companion extension, `/chrome-doctor` checks connectivity and version drift, screenshots save to disk, and the prompt primer tells agents to inspect with `chrome_snapshot` before acting and avoid destructive actions unless explicitly requested.
 
 ## Install
 
@@ -53,14 +53,16 @@ Then in Chrome:
 4. Return to Pi and run:
 
 ```text
-/chrome-status
+/chrome-doctor
 ```
 
-Expected messages:
+Expected output:
 
 ```text
 Performing Chrome bridge health check
-Chrome profile bridge connected (ID: <chrome-extension-id>)
+pi-chrome v<version>
+• Local bridge: mode=server, url=http://127.0.0.1:17318
+✓ Companion Chrome extension responding (ID: <chrome-extension-id>, ext v<version>)
 ```
 
 ## Foreground control
@@ -115,8 +117,7 @@ Screenshots save under `.pi/chrome-screenshots/` by default, which composes nice
 
 ## Diagnostics
 
-- `/chrome-status` — quick health check; reports the connected Chrome extension ID and version.
-- `/chrome-doctor` — deeper diagnosis with one-line fixes for common setup failures (extension not loaded, bridge owner stale after `pi update`, version mismatch between pi-chrome and the loaded Chrome extension).
+- `/chrome-doctor` — single command that checks connectivity and reports the loaded Chrome extension ID + version, plus a one-line fix for common setup failures (extension not loaded, bridge owner stale after `pi update`, version mismatch between pi-chrome and the loaded Chrome extension).
 
 If the Chrome extension you have loaded is older than `pi-chrome` on disk, `/chrome-doctor` will tell you to reload it from `chrome://extensions`.
 

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

@@ -1,7 +1,7 @@
 {
   "manifest_version": 3,
   "name": "Pi Existing Chrome Profile Bridge",
-  "version": "0.4.3",
+  "version": "0.5.0",
   "description": "Lets Pi control tabs in this existing Chrome profile via a local bridge at 127.0.0.1.",
   "permissions": ["tabs", "scripting", "storage", "activeTab", "alarms"],
   "host_permissions": ["<all_urls>", "http://127.0.0.1:17318/*"],

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

@@ -46,7 +46,7 @@ type BridgeResult = {
 	error?: string;
 };
 
-const PI_CHROME_VERSION = "0.4.3";
+const PI_CHROME_VERSION = "0.5.0";
 const DEFAULT_HOST = process.env.PI_CHROME_BRIDGE_HOST ?? "127.0.0.1";
 const DEFAULT_PORT = Number(process.env.PI_CHROME_BRIDGE_PORT ?? "17318");
 const DEFAULT_TIMEOUT_MS = 30_000;
@@ -274,7 +274,24 @@ class ChromeProfileBridge {
 		if (request.method === "GET" && url.pathname === "/next") {
 			this.lastSeenAt = Date.now();
 			this.clientName = url.searchParams.get("name") ?? undefined;
-			const command = this.queue.shift() ?? (await this.waitForCommand(25_000));
+			let aborted = false;
+			let activeWaiter: ((command: BridgeCommand | undefined) => void) | undefined;
+			request.once("close", () => {
+				aborted = true;
+				if (activeWaiter) this.waiters = this.waiters.filter((entry) => entry !== activeWaiter);
+			});
+			let command = this.queue.shift();
+			if (!command) {
+				command = await this.waitForCommand(25_000, (waiter) => {
+					activeWaiter = waiter;
+				});
+			}
+			if (aborted) {
+				// Long-poll connection died before we could deliver. Requeue any command we pulled
+				// so the next live /next picks it up instead of dropping it on the floor.
+				if (command) this.queue.unshift(command);
+				return;
+			}
 			sendJson(response, 200, command ? { type: "command", command } : { type: "none" });
 			return;
 		}
@@ -296,16 +313,22 @@ class ChromeProfileBridge {
 		sendJson(response, 404, { error: "not found" });
 	}
 
-	private waitForCommand(timeoutMs: number): Promise<BridgeCommand | undefined> {
+	private waitForCommand(
+		timeoutMs: number,
+		registerWaiter?: (waiter: (command: BridgeCommand | undefined) => void) => void,
+	): Promise<BridgeCommand | undefined> {
 		return new Promise((resolveWait) => {
-			const timer = setTimeout(() => {
-				this.waiters = this.waiters.filter((waiter) => waiter !== resolveWait);
-				resolveWait(undefined);
-			}, timeoutMs);
-			this.waiters.push((command) => {
+			let settled = false;
+			const waiter = (command: BridgeCommand | undefined) => {
+				if (settled) return;
+				settled = true;
 				clearTimeout(timer);
+				this.waiters = this.waiters.filter((entry) => entry !== waiter);
 				resolveWait(command);
-			});
+			};
+			const timer = setTimeout(() => waiter(undefined), timeoutMs);
+			this.waiters.push(waiter);
+			registerWaiter?.(waiter);
 		});
 	}
 }
@@ -347,31 +370,16 @@ If chrome_* tools time out, ask the user to run /chrome-onboard, then load the b
 		return { systemPrompt: event.systemPrompt + primer };
 	});
 
-	pi.registerCommand("chrome-status", {
-		description: "Run an explicit health check against the existing-profile Chrome companion extension",
-		handler: async (_args, ctx) => {
-			ctx.ui.notify("Performing Chrome bridge health check", "info");
-			try {
-				const version = (await bridge.send("tab.version", {}, 35_000)) as { extensionId?: string; extensionVersion?: string };
-				const suffix = [version.extensionId ? `ID: ${version.extensionId}` : null, version.extensionVersion ? `ext v${version.extensionVersion}` : null]
-					.filter(Boolean)
-					.join(", ");
-				ctx.ui.notify(suffix ? `Chrome profile bridge connected (${suffix})` : "Chrome profile bridge connected", "info");
-			} catch (error) {
-				ctx.ui.notify(`Chrome bridge health check failed: ${(error as Error).message}`, "warning");
-			}
-		},
-	});
-
 	pi.registerCommand("chrome-doctor", {
 		description:
-			"Diagnose Chrome bridge setup. Checks the local bridge, the companion Chrome extension, and reports a one-line fix for common failures.",
+			"Check Chrome bridge connectivity and diagnose setup. Reports the local bridge, companion Chrome extension status (ID + version), and a one-line fix for common failures (extension not loaded, stale service worker, version drift).",
 		handler: async (_args, ctx) => {
+			ctx.ui.notify("Performing Chrome bridge health check", "info");
 			const lines: string[] = [`pi-chrome v${PI_CHROME_VERSION}`];
 			const status = bridge.status();
 			lines.push(`• Local bridge: mode=${status.mode}, url=${status.url}`);
 			try {
-				const version = (await bridge.send("tab.version", {}, 8_000)) as {
+				const version = (await bridge.send("tab.version", {}, 35_000)) as {
 					extensionId?: string;
 					extensionVersion?: string;
 				};
@@ -440,7 +448,7 @@ If chrome_* tools time out, ask the user to run /chrome-onboard, then load the b
 				await pi.exec("sh", ["-lc", `printf %s ${JSON.stringify(extensionPath)} | pbcopy`], { cwd: workspaceCwd(ctx), timeout: 5_000 }).catch(() => undefined);
 			}
 			ctx.ui.notify(
-				"Chrome bridge setup opened. The extension path has been copied to your clipboard. After loading it, run /chrome-status.",
+				"Chrome bridge setup opened. The extension path has been copied to your clipboard. After loading it, run /chrome-doctor.",
 				"info",
 			);
 		},

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-chrome",
-  "version": "0.4.3",
+  "version": "0.5.0",
   "description": "Drive your existing logged-in Chrome from Pi \u2014 no re-login, no throwaway profile, background by default.",
   "keywords": [
     "pi-package",