pi-chrome 0.1.2 → 0.2.1

package/README.md

@@ -4,6 +4,8 @@ Control the Chrome profile you already use from Pi.
 
 `pi-chrome` gives Pi agents browser tools for your **real Chrome windows, tabs, and authenticated sessions**. It uses a companion Chrome extension instead of the Chrome DevTools Protocol (CDP), so it does not launch a throwaway debug browser profile and does not require re-signing into the apps you already have open.
 
+Multiple Pi sessions can use Chrome at the same time. The first Pi session starts the local bridge; later sessions automatically detect that bridge and submit their Chrome commands through it.
+
 ## Why try it?
 
 - **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.
@@ -89,6 +91,8 @@ These tools are especially useful for authenticated web app debugging, repro flo
 
 Pi starts a local bridge on `127.0.0.1:17318`. The companion Chrome extension, installed in your normal Chrome profile, polls that local bridge for commands and executes them using Chrome extension APIs.
 
+If another Pi session is already running the bridge, additional Pi sessions automatically act as clients of that shared bridge. This lets planner/audit/worker sessions all use the same authenticated Chrome profile concurrently without fighting over the port.
+
 This is intentionally different from CDP-based tools: the browser extension lives inside the profile you already use, so Pi can interact with existing tabs and authenticated page state.
 
 ## Security model

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

@@ -111,6 +111,7 @@ class ChromeProfileBridge {
 	private waiters: Array<(command: BridgeCommand | undefined) => void> = [];
 	private lastSeenAt: number | undefined;
 	private clientName: string | undefined;
+	private mode: "server" | "client" | undefined;
 
 	constructor(
 		private readonly host: string,
@@ -131,6 +132,7 @@ class ChromeProfileBridge {
 	status(): Record<string, unknown> {
 		return {
 			url: this.url,
+			mode: this.mode ?? "starting",
 			connected: this.connected,
 			lastSeenAt: this.lastSeenAt,
 			clientName: this.clientName,
@@ -140,22 +142,36 @@ class ChromeProfileBridge {
 	}
 
 	async start(): Promise<void> {
-		if (this.server) return;
+		if (this.server || this.mode === "client") return;
 		this.server = createServer((request, response) => {
 			void this.handle(request, response).catch((error) => {
 				sendJson(response, 500, { error: (error as Error).message });
 			});
 		});
-		await new Promise<void>((resolveStart, rejectStart) => {
-			this.server!.once("error", rejectStart);
-			this.server!.listen(this.port, this.host, () => {
-				this.server!.off("error", rejectStart);
-				resolveStart();
+		try {
+			await new Promise<void>((resolveStart, rejectStart) => {
+				this.server!.once("error", rejectStart);
+				this.server!.listen(this.port, this.host, () => {
+					this.server!.off("error", rejectStart);
+					resolveStart();
+				});
 			});
-		});
+			this.mode = "server";
+		} catch (error) {
+			this.server.close();
+			this.server = undefined;
+			if ((error as NodeJS.ErrnoException).code !== "EADDRINUSE") throw error;
+			// Another Pi session already owns the bridge port. Use it as the shared
+			// machine-local broker so multiple Pi sessions can control Chrome at once.
+			this.mode = "client";
+		}
 	}
 
 	stop(): void {
+		if (this.mode === "client") {
+			this.mode = undefined;
+			return;
+		}
 		for (const pending of this.pending.values()) {
 			clearTimeout(pending.timer);
 			pending.reject(new Error("Chrome profile bridge stopped"));
@@ -166,9 +182,15 @@ class ChromeProfileBridge {
 		this.waiters = [];
 		this.server?.close();
 		this.server = undefined;
+		this.mode = undefined;
 	}
 
 	send(action: string, params: Record<string, unknown>, timeoutMs = DEFAULT_TIMEOUT_MS): Promise<unknown> {
+		if (this.mode === "client") return this.sendViaOwner(action, params, timeoutMs);
+		return this.sendLocal(action, params, timeoutMs);
+	}
+
+	private sendLocal(action: string, params: Record<string, unknown>, timeoutMs = DEFAULT_TIMEOUT_MS): Promise<unknown> {
 		const id = `${Date.now().toString(36)}-${Math.random().toString(36).slice(2)}`;
 		const command = { id, action, params };
 		return new Promise((resolveCommand, rejectCommand) => {
@@ -186,6 +208,34 @@ class ChromeProfileBridge {
 		});
 	}
 
+	private async sendViaOwner(action: string, params: Record<string, unknown>, timeoutMs: number): Promise<unknown> {
+		const controller = new AbortController();
+		const timer = setTimeout(() => controller.abort(), timeoutMs + 2_000);
+		try {
+			const response = await fetch(`${this.url}/command`, {
+				method: "POST",
+				headers: { "content-type": "application/json" },
+				body: JSON.stringify({ action, params, timeoutMs }),
+				signal: controller.signal,
+			});
+			const payload = (await response.json().catch(() => ({}))) as { ok?: boolean; result?: unknown; error?: string };
+			if (response.status === 404) {
+				throw new Error(
+					"A running Pi session owns the Chrome bridge but is using an older pi-chrome without multi-session support. Restart that Pi session after `pi update`, then retry.",
+				);
+			}
+			if (!response.ok || !payload.ok) throw new Error(payload.error ?? `Chrome bridge owner HTTP ${response.status}`);
+			return payload.result;
+		} catch (error) {
+			if ((error as Error).name === "AbortError") {
+				throw new Error(`Timed out waiting for shared Chrome bridge owner after ${timeoutMs}ms`);
+			}
+			throw error;
+		} finally {
+			clearTimeout(timer);
+		}
+	}
+
 	private enqueue(command: BridgeCommand): void {
 		const waiter = this.waiters.shift();
 		if (waiter) waiter(command);
@@ -202,6 +252,24 @@ class ChromeProfileBridge {
 			sendJson(response, 200, this.status());
 			return;
 		}
+		if (request.method === "POST" && url.pathname === "/command") {
+			const body = JSON.parse(await readRequestBody(request)) as {
+				action?: string;
+				params?: Record<string, unknown>;
+				timeoutMs?: number;
+			};
+			if (!body.action) {
+				sendJson(response, 400, { ok: false, error: "Missing command action" });
+				return;
+			}
+			try {
+				const result = await this.sendLocal(body.action, body.params ?? {}, body.timeoutMs ?? DEFAULT_TIMEOUT_MS);
+				sendJson(response, 200, { ok: true, result });
+			} catch (error) {
+				sendJson(response, 504, { ok: false, error: (error as Error).message });
+			}
+			return;
+		}
 		if (request.method === "GET" && url.pathname === "/next") {
 			this.lastSeenAt = Date.now();
 			this.clientName = url.searchParams.get("name") ?? undefined;
@@ -283,8 +351,8 @@ If chrome_* tools time out, ask the user to run /chrome-onboard, then load the b
 						: "Chrome profile bridge connected",
 					"info",
 				);
-			} catch {
-				ctx.ui.notify("Chrome bridge health check timed out. Run /chrome-onboard to connect Chrome.", "warning");
+			} catch (error) {
+				ctx.ui.notify(`Chrome bridge health check failed: ${(error as Error).message}`, "warning");
 			}
 		},
 	});

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "pi-chrome",
-  "version": "0.1.2",
-  "description": "Control your existing authenticated Chrome profile from Pi with tabs, snapshots, clicks, typing, JS evaluation, waits, and screenshots.",
+  "version": "0.2.1",
+  "description": "Control your existing authenticated Chrome profile from one or more Pi sessions with tabs, snapshots, clicks, typing, JS evaluation, waits, and screenshots.",
   "keywords": [
     "pi-package",
     "pi-extension",