pi-chrome 0.11.4 → 0.12.0

package/README.md

@@ -11,9 +11,9 @@ Multiple Pi sessions can use Chrome at the same time. The first Pi session start
 ## 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.
-- **Watch your authenticated Chrome work** — by default, `chrome_*` tool calls focus Chrome and activate the target tab so you can see the agent inspect, navigate, click, and type in real time. Switch to silent/background mode for the whole session with `/chrome-background`, or pass `background: true` on a single tool call when you want quiet.
+- **Watch your authenticated Chrome work** — by default, `chrome_*` tool calls focus Chrome and activate the target tab so you can see the agent inspect, navigate, click, and type in real time. Switch to silent/background mode for the whole session with `/chrome settings background`, or pass `background: true` on a single tool call when you want quiet.
 - **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-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.
+- **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
 
@@ -29,14 +29,14 @@ pi install ./pi-chrome
 
 ### Why an unpacked Chrome extension?
 
-`pi-chrome` cannot ship through the Chrome Web Store: a Web Store extension is not allowed to talk to a local bridge controlled by another tool. Instead it ships as a small, MIT-licensed unpacked extension in `extensions/chrome-profile-bridge/browser-extension/` — read the source before loading. `/chrome-doctor` reports the loaded extension version and warns when it drifts from the installed `pi-chrome`.
+`pi-chrome` cannot ship through the Chrome Web Store: a Web Store extension is not allowed to talk to a local bridge controlled by another tool. Instead it ships as a small, MIT-licensed unpacked extension in `extensions/chrome-profile-bridge/browser-extension/` — read the source before loading. `/chrome doctor` reports the loaded extension version and warns when it drifts from the installed `pi-chrome`.
 
 ## First-time setup
 
 In Pi, run:
 
 ```text
-/chrome-onboard
+/chrome onboard
 ```
 
 Pi first shows setup instructions and waits for confirmation. Press Enter to continue. On macOS it will:
@@ -53,7 +53,7 @@ Then in Chrome:
 4. Return to Pi and run:
 
 ```text
-/chrome-doctor
+/chrome doctor
 ```
 
 Expected output:
@@ -65,24 +65,25 @@ pi-chrome v<version>
 ✓ Companion Chrome extension responding (ID: <chrome-extension-id>, ext v<version>)
 ```
 
-## Trusted-input mode (CDP)
+## Click modes
 
-By default, `chrome_*` clicks and keystrokes are **synthetic** DOM events (`event.isTrusted === false`). They drive React/Vue/Angular state correctly but **do not** satisfy Chrome's user-activation gates: clipboard write, fullscreen, file picker, and autoplay all need a real user gesture.
+pi-chrome can drive Chrome two ways:
 
-pi-chrome can optionally route input through `chrome.debugger` (CDP `Input.dispatchMouseEvent` / `Input.dispatchKeyEvent`) so each event arrives as `isTrusted=true`, satisfies user-activation, and bypasses site bot-detection that filters synthetic events. The tradeoff: Chrome pins a *"Pi Chrome Connector started debugging this browser"* banner to the top of any debugged tab.
+- **Quiet clicks** — fast and unobtrusive. They work on most sites, but some pages (sign-in flows, copy-to-clipboard buttons, file pickers, autoplay videos, fullscreen, paywalls) ignore them because they don't look like a real human action.
+- **Real-looking clicks** — indistinguishable from a person clicking. They unlock the cases above, but Chrome shows a *"Pi Chrome Connector started debugging this browser"* banner at the top of every tab pi-chrome touches while it's working.
 
-Usage:
+Pick a mode with `/chrome settings trusted`:
 
 ```text
-/chrome-trusted on       # all chrome_* tools dispatch via CDP
-/chrome-trusted off      # synthetic events only (default)
-/chrome-trusted auto     # CDP only when a tool passes trusted=true
-/chrome-trusted status   # show current mode and attached tabs
+/chrome settings trusted auto     # default; quiet by default, real-looking only when needed
+/chrome settings trusted off      # always quiet, no banner ever
+/chrome settings trusted on       # always real-looking, banner stays up the whole session
+/chrome settings trusted status   # show the current mode
 ```
 
-For a single call, pass `trusted: true` on `chrome_click`, `chrome_type`, `chrome_fill`, `chrome_key`, `chrome_hover`, `chrome_drag`, or `chrome_scroll`. The per-call value always wins over the session toggle.
+For a one-off call, pass `trusted: true` (or `false`) on `chrome_click`, `chrome_type`, `chrome_fill`, `chrome_key`, `chrome_hover`, `chrome_drag`, or `chrome_scroll`. The per-call value wins over the global mode.
 
-First time you upgrade to a pi-chrome that uses trusted input, Chrome will prompt to re-approve the extension's new `debugger` permission — do that once in `chrome://extensions`.
+First time you update pi-chrome to a version that supports real-looking clicks, Chrome will ask you to re-approve the extension. Open `chrome://extensions` and accept the new permission once.
 
 ## Background mode
 
@@ -91,9 +92,9 @@ By default, `chrome_*` tools focus Chrome and activate the target tab so you can
 When you want quiet (planner / audit / worker sessions running alongside your editor), turn background mode on for the whole Pi session:
 
 ```text
-/chrome-background          # toggle
-/chrome-background on       # explicit
-/chrome-background off      # explicit
+/chrome settings background          # toggle
+/chrome settings background on       # explicit
+/chrome settings background off      # explicit
 ```
 
 For a single tool call, the agent can pass `background: true` directly. The per-call value always wins over the session toggle.
@@ -136,9 +137,9 @@ Screenshots save under `.pi/chrome-screenshots/` by default, which composes nice
 
 ## Diagnostics
 
-- `/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).
+- `/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`.
+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`.
 
 ## Compose with
 

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

@@ -1,7 +1,7 @@
 {
   "manifest_version": 3,
   "name": "Pi Chrome Connector",
-  "version": "0.11.4",
+  "version": "0.12.0",
   "description": "Lets Pi control tabs in Chrome via a local connector at 127.0.0.1.",
   "permissions": ["tabs", "scripting", "storage", "activeTab", "alarms", "webNavigation", "debugger"],
   "host_permissions": ["<all_urls>", "http://127.0.0.1:17318/*"],

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

@@ -233,7 +233,7 @@ class ChromeProfileBridge {
 				this.queue = this.queue.filter((queued) => queued.id !== id);
 				rejectCommand(
 					new Error(
-						`Timed out waiting for Chrome extension after ${timeoutMs}ms. Run /chrome-onboard, then load the bundled browser-extension folder in your normal Chrome profile.`,
+						`Timed out waiting for Chrome extension after ${timeoutMs}ms. Run /chrome onboard, then load the bundled browser-extension folder in your normal Chrome profile.`,
 					),
 				);
 			}, timeoutMs);
@@ -415,8 +415,8 @@ export default function (pi: ExtensionAPI): void {
 		ctx.ui.setStatus("chrome", `Chrome bridge :${DEFAULT_PORT}`);
 		ctx.ui.notify(
 			status.mode === "client"
-				? `Chrome profile bridge connected to shared bridge at ${bridge.url}.`
-				: `Chrome profile bridge listening at ${bridge.url}. Run /chrome-onboard to load the bundled browser extension in your normal Chrome profile.`,
+				? `pi-chrome connected (sharing the Chrome connection an earlier pi session opened).`
+				: `pi-chrome is ready and waiting for the Chrome companion to connect. Run /chrome onboard to install it.`,
 			"info",
 		);
 	});
@@ -440,21 +440,20 @@ Usage rules:
 2. \`includeSnapshot=true\` on click/type/fill to verify in one round trip.
 3. If \`chrome_evaluate\` returns null when you expected a value, the expression evaluated to null/undefined in the page; surface the value via \`JSON.stringify\` to confirm.
 4. \`chrome_navigate\` supports an optional \`initScript\` that runs at document_start in MAIN world for the next navigation (good for seeding localStorage or stubbing Date.now).
-5. By default chrome_* tools focus Chrome so the user can watch; pass \`background=true\` or run /chrome-background to silence the whole session.
+5. By default chrome_* tools focus Chrome so the user can watch; pass \`background=true\` or run /chrome settings background to silence the whole session.
 6. If you hit an autoplay/clipboard/file-picker gate, tell the user; this bridge cannot satisfy it.
-7. Run /chrome-doctor when in doubt about connectivity or capabilities.
+7. Run /chrome doctor when in doubt about connectivity or capabilities.
 </chrome-profile-bridge>`;
 		return { systemPrompt: event.systemPrompt + primer };
 	});
 
-	pi.registerCommand("chrome-doctor", {
-		description:
-			"Check Chrome bridge connectivity and capability tier. Probes the local bridge, the companion Chrome extension, MAIN-world evaluation, and CDP availability, and prints one-line fixes for common failures.",
-		handler: async (_args, ctx) => {
-			ctx.ui.notify("Performing Chrome bridge health check", "info");
+	// Shared handlers, dispatched by the unified /chrome command below.
+	const doctorHandler = async (ctx: ExtensionContext) => {
+			ctx.ui.notify("Checking pi-chrome…", "info");
 			const lines: string[] = [`pi-chrome v${PI_CHROME_VERSION}`];
 			const status = bridge.status();
-			lines.push(`• Local bridge: mode=${status.mode}, url=${status.url}`);
+			const roleLabel = status.mode === "client" ? "sharing another pi session's connection" : "running the Chrome connection for this machine";
+			lines.push(`• This pi session is ${roleLabel}.`);
 			let extensionAlive = false;
 			let versionMismatch = false;
 			try {
@@ -469,44 +468,44 @@ Usage rules:
 				if (version.extensionVersion && version.extensionVersion !== PI_CHROME_VERSION) {
 					versionMismatch = true;
 					lines.push(
-						`✗ EXTENSION VERSION MISMATCH: companion extension is v${version.extensionVersion}, but pi-chrome is v${PI_CHROME_VERSION}.`,
-						`  All chrome_* tools will run with the OLD extension code until this is fixed.`,
-						`  Fix: open chrome://extensions and click reload on "Pi Chrome Connector".`,
-						`  (Future version drifts will self-heal: the extension now polls pi-chrome's expected version and reloads itself.)`,
+						`✗ The Chrome companion extension is on an old version (${version.extensionVersion}); this pi-chrome is ${PI_CHROME_VERSION}.`,
+						`  Every Chrome action will run with the old code until you reload the extension.`,
+						`  Fix: open chrome://extensions and click the refresh icon on 'Pi Chrome Connector'.`,
+						`  (After this one-time fix, future updates reload automatically.)`,
 					);
 				} else {
-					lines.push(`✓ Companion Chrome extension responding (ID: ${version.extensionId ?? "?"}, ext v${version.extensionVersion ?? "?"}, latency ${latencyMs}ms)`);
+					lines.push(`✓ Chrome is connected (companion extension v${version.extensionVersion ?? "?"}, responded in ${latencyMs}ms).`);
 				}
 			} catch (error) {
 				const message = (error as Error).message;
-				lines.push(`✗ Companion Chrome extension not responding: ${message}`);
+				lines.push(`✗ Chrome isn't responding: ${message}`);
 				if (message.includes("older pi-chrome without multi-session")) {
-					lines.push("  Fix: restart the Pi session that owns the bridge (it was started on an older pi-chrome).");
+					lines.push("  Fix: quit and restart the pi session that first opened the Chrome connection (it was on an older pi-chrome).");
 				} else {
-					lines.push("  Fix: run /chrome-onboard, then load the bundled browser-extension folder in chrome://extensions and keep that Chrome window open.");
+					lines.push("  Fix: run /chrome onboard to install the Chrome companion extension, then keep that Chrome window open.");
 				}
 			}
 
 			if (extensionAlive && !versionMismatch) {
-				// MAIN-world evaluate probe.
+				// Sanity-check that pi-chrome can actually run code in the active tab.
 				try {
 					const value = await bridge.send("page.evaluate", { expression: "1+1", awaitPromise: true, foreground: false }, 10_000);
-					if (value === 2) lines.push(`✓ chrome_evaluate("1+1") = 2`);
-					else lines.push(`⚠ chrome_evaluate("1+1") returned ${JSON.stringify(value)} (expected 2). The current tab may have a restrictive CSP or be a chrome:// URL.`);
+					if (value === 2) lines.push(`✓ pi-chrome can run code in the active Chrome tab.`);
+					else lines.push(`⚠ pi-chrome ran code in the active tab but got an unexpected result (${JSON.stringify(value)}). The current tab may be locked-down (a Chrome internal page or a strict site).`);
 				} catch (error) {
-					lines.push(`✗ chrome_evaluate failed: ${(error as Error).message}`);
+					lines.push(`✗ pi-chrome can't run code in the active tab: ${(error as Error).message}`);
 				}
 
-				// Capability probe via MAIN-world helper.
+				// Surface obvious site-side automation flags so the user knows why a site might block pi.
 				try {
 					const probe = (await bridge.send("page.probe", { foreground: false }, 10_000)) as Record<string, unknown>;
-					if (probe && probe.arithmetic === 2) lines.push(`✓ MAIN-world helper injection works (location=${hostnameOf(String(probe.location))})`);
-					if (probe && probe.webdriver) lines.push(`⚠ navigator.webdriver=true on current tab — site fingerprinting may flag automation.`);
+					if (probe && probe.arithmetic === 2) lines.push(`✓ The active tab is ${hostnameOf(String(probe.location))} and accepts pi-chrome's commands.`);
+					if (probe && probe.webdriver) lines.push(`⚠ Your Chrome is reporting itself as automated to websites. Some sites use this signal to block sign-ins or bot checks.`);
 				} catch (error) {
-					lines.push(`⚠ page.probe failed: ${(error as Error).message}`);
+					lines.push(`⚠ Couldn't inspect the active tab: ${(error as Error).message}`);
 				}
 			} else if (versionMismatch) {
-				lines.push(`… Skipped MAIN-world capability checks because the loaded extension is stale.`);
+				lines.push(`… Skipped the remaining checks until you reload the Chrome extension.`);
 			}
 
 			// Real-input mode probe (plain English for the user).
@@ -524,7 +523,7 @@ Usage rules:
 								? " Clicks/keys are quiet by default; if a site rejects a quiet click, pi-chrome retries it once with a real-looking click. The Chrome banner shows only when that retry happens."
 								: status.mode === "on"
 									? " Every click and keystroke uses a real-looking event. The Chrome banner stays up on every tab pi-chrome touches."
-									: " All clicks are quiet, no banner. Some sites (sign-ins, copy buttons, file pickers, paywalls) may silently ignore them. Switch to /chrome-trusted auto if a site isn’t responding.";
+									: " All clicks are quiet, no banner. Some sites (sign-ins, copy buttons, file pickers, paywalls) may silently ignore them. Switch to /chrome settings trusted auto if a site isn’t responding.";
 						const label = status.mode === "auto" ? "auto (smart upgrade)" : status.mode === "on" ? "on (always real-looking)" : "off (always quiet)";
 						lines.push(`✓ Click mode: ${label}${banner}.${note}`);
 					} else {
@@ -535,25 +534,10 @@ Usage rules:
 				}
 			}
 
-			ctx.ui.notify(lines.join("\n"), "info");
-		},
-	});
+		ctx.ui.notify(lines.join("\n"), "info");
+	};
 
-	pi.registerCommand("chrome-trusted", {
-		description:
-			"Choose how realistically pi-chrome should drive Chrome. Real-looking clicks/keys unlock things like copy-to-clipboard buttons, file pickers, and sign-in pages, but show a banner at the top of every Chrome window saying it's being driven by pi-chrome. Three modes:\n  auto (default) — quiet by default; auto-upgrade when a site blocks the quiet click.\n  off — always quiet, no banner; some sites won't accept these clicks.\n  on — always real-looking, banner stays up the whole session.\n  status — show the current mode.",
-		getArgumentCompletions: (prefix) => {
-			const items = [
-				{ value: "auto", label: "auto", description: "Default. Quiet clicks; upgrade to real ones only when a site rejects them." },
-				{ value: "off", label: "off", description: "Always quiet. No banner. Some sites won't accept the clicks." },
-				{ value: "on", label: "on", description: "Always real-looking clicks. Yellow banner stays up. Best for stubborn sites." },
-				{ value: "status", label: "status", description: "Show the current mode." },
-			];
-			const lowered = prefix.toLowerCase();
-			const matches = items.filter((item) => item.value.startsWith(lowered));
-			return matches.length > 0 ? matches : null;
-		},
-		handler: async (args, ctx) => {
+	const trustedHandler = async (ctx: ExtensionContext, args: string) => {
 			const rawArg = (args || "").trim().toLowerCase();
 
 			// Resolve current status once for both branches (interactive picker + direct args).
@@ -611,7 +595,7 @@ Usage rules:
 			}
 
 			if (!["on", "off", "auto"].includes(target)) {
-				ctx.ui.notify(`Unknown choice '${rawArg}'. Pick one of: auto | off | on | status, or just run /chrome-trusted with no argument.`, "warning");
+				ctx.ui.notify(`Unknown choice '${rawArg}'. Pick one of: auto | off | on | status, or run /chrome settings trusted with no argument.`, "warning");
 				return;
 			}
 
@@ -645,58 +629,129 @@ Usage rules:
 					ctx.ui.notify("Auto. Clicks stay quiet by default; pi-chrome will only switch to real-looking clicks when a site rejects a quiet one. The Chrome banner will appear only when that retry happens.", "info");
 				}
 			} catch (error) {
-				ctx.ui.notify(`Couldn't switch mode: ${(error as Error).message}`, "warning");
-			}
-		},
-	});
+			ctx.ui.notify(`Couldn't switch mode: ${(error as Error).message}`, "warning");
+		}
+	};
+
+	const backgroundHandler = async (ctx: ExtensionContext, args: string) => {
+		const arg = (args || "").trim().toLowerCase();
+		if (arg === "on" || arg === "true" || arg === "1") backgroundDefault = true;
+		else if (arg === "off" || arg === "false" || arg === "0") backgroundDefault = false;
+		else backgroundDefault = !backgroundDefault;
+		ctx.ui.notify(
+			backgroundDefault
+				? "Quiet mode on. pi-chrome will work in the background; Chrome won't steal focus."
+				: "Watch mode on. Chrome will pop to the front and switch tabs so you can see what pi-chrome is doing.",
+			"info",
+		);
+	};
+
+	const onboardHandler = async (ctx: ExtensionContext) => {
+		const extensionPath = browserExtensionPath();
+		const proceed = await ctx.ui.confirm(
+			"Install the pi-chrome Chrome extension?",
+			`This opens Chrome's extensions page and reveals the folder pi-chrome needs you to load.\n\nWhen the windows open, in Chrome:\n  1. Turn on 'Developer mode' (top-right toggle).\n  2. Click 'Load unpacked' and choose the folder that just opened in Finder, or paste this path:\n     ${extensionPath}\n\nPress Enter to continue, or Esc to cancel.`,
+		);
+		if (!proceed) {
+			ctx.ui.notify("Cancelled. You can run /chrome onboard again whenever you're ready.", "info");
+			return;
+		}
+		if (process.platform === "darwin") {
+			await pi.exec("open", ["-a", "Google Chrome", "chrome://extensions"], { cwd: workspaceCwd(ctx), timeout: 5_000 }).catch(() => undefined);
+			await pi.exec("open", ["-R", extensionPath], { cwd: workspaceCwd(ctx), timeout: 5_000 }).catch(() => undefined);
+			await pi.exec("sh", ["-lc", `printf %s ${JSON.stringify(extensionPath)} | pbcopy`], { cwd: workspaceCwd(ctx), timeout: 5_000 }).catch(() => undefined);
+		}
+		ctx.ui.notify(
+			"Chrome and Finder should be open. The extension folder path is on your clipboard. After you click 'Load unpacked' and pick it, run /chrome doctor to confirm everything is connected.",
+			"info",
+		);
+	};
+
+	const settingsHandler = async (ctx: ExtensionContext, rest: string[]) => {
+		if (rest.length === 0) {
+			const picked = await ctx.ui.select(
+				"pi-chrome settings — what would you like to change?",
+				[
+					"background — should Chrome pop to the front when pi-chrome acts, or work silently?",
+					"trusted — how realistic should pi-chrome's clicks and keystrokes be?",
+				],
+			);
+			if (!picked) return;
+			if (picked.startsWith("background")) return backgroundHandler(ctx, "");
+			if (picked.startsWith("trusted")) return trustedHandler(ctx, "");
+			return;
+		}
+		const [head, ...sub] = rest;
+		const subArgs = sub.join(" ");
+		switch (head) {
+			case "background": return backgroundHandler(ctx, subArgs);
+			case "trusted": return trustedHandler(ctx, subArgs);
+			default:
+				ctx.ui.notify(`Unknown setting '${head}'. Try: /chrome settings background | trusted.`, "warning");
+		}
+	};
 
-	pi.registerCommand("chrome-background", {
+	pi.registerCommand("chrome", {
 		description:
-			"Toggle silent/background mode for chrome_* tools. Background ON: chrome_* tools act silently — your editor/terminal keeps focus, Chrome does not pop up, your workflow is not interrupted. Background OFF (default): Chrome focuses and activates the target tab so you can watch the agent work, useful for demos, pair-driving, and debugging — tradeoff: Chrome pops up and steals focus. Pass `on` / `off` to set explicitly, or no argument to toggle.",
+			"All pi-chrome controls in one place. Subcommands:\n  /chrome doctor — quick health check.\n  /chrome onboard — install the Chrome companion extension.\n  /chrome settings — change how pi-chrome behaves (background mode, click realism).\nRun with no arguments for an interactive picker.",
 		getArgumentCompletions: (prefix) => {
-			const items = [
-				{ value: "on", label: "on", description: "Run chrome_* actions silently without focusing Chrome" },
-				{ value: "off", label: "off", description: "Bring Chrome to the foreground for chrome_* actions (default)" },
+			const rawTokens = prefix.split(/\s+/);
+			const last = (rawTokens[rawTokens.length - 1] ?? "").toLowerCase();
+			const path = rawTokens.slice(0, -1).filter(Boolean).map((t) => t.toLowerCase());
+
+			const TOP = [
+				{ value: "doctor", description: "Quick health check. Tells you if Chrome is connected and what's wrong if it isn't." },
+				{ value: "onboard", description: "Install the Chrome companion extension (first-time setup)." },
+				{ value: "settings", description: "Change pi-chrome behaviour: background mode, click realism." },
 			];
-			const lowered = prefix.toLowerCase();
-			const matches = items.filter((item) => item.value.startsWith(lowered));
-			return matches.length > 0 ? matches : null;
+			const SETTINGS = [
+				{ value: "background", description: "Should Chrome pop to the front when pi-chrome acts, or work silently?" },
+				{ value: "trusted", description: "How realistic should pi-chrome's clicks and keystrokes be?" },
+			];
+			const BG = [
+				{ value: "on", description: "Work silently. Chrome stays in the background. Your editor keeps focus." },
+				{ value: "off", description: "Bring Chrome to the front so you can watch (default)." },
+			];
+			const TRUSTED = [
+				{ value: "auto", description: "Default. Quiet clicks; upgrade to real ones only when a site rejects them." },
+				{ value: "off", description: "Always quiet. No banner. Some sites won't accept the clicks." },
+				{ value: "on", description: "Always real-looking clicks. Banner stays up. Best for stubborn sites." },
+				{ value: "status", description: "Show the current click mode." },
+			];
+
+			let pool: Array<{ value: string; description: string }> | null = null;
+			if (path.length === 0) pool = TOP;
+			else if (path[0] === "settings" && path.length === 1) pool = SETTINGS;
+			else if (path[0] === "settings" && path[1] === "background" && path.length === 2) pool = BG;
+			else if (path[0] === "settings" && path[1] === "trusted" && path.length === 2) pool = TRUSTED;
+			if (!pool) return null;
+
+			const items = pool.map((p) => ({ value: p.value, label: p.value, description: p.description }));
+			const filtered = items.filter((i) => i.value.startsWith(last));
+			return filtered.length > 0 ? filtered : null;
 		},
 		handler: async (args, ctx) => {
-			const arg = (args || "").trim().toLowerCase();
-			if (arg === "on" || arg === "true" || arg === "1") backgroundDefault = true;
-			else if (arg === "off" || arg === "false" || arg === "0") backgroundDefault = false;
-			else backgroundDefault = !backgroundDefault;
-			ctx.ui.notify(
-				backgroundDefault
-					? "Chrome background mode ON. chrome_* tools will run silently. Your current app keeps focus."
-					: "Chrome background mode OFF. chrome_* tools will focus Chrome and activate the target tab so you can watch the agent work.",
-				"info",
-			);
-		},
-	});
-
-	pi.registerCommand("chrome-onboard", {
-		description: "Guide Chrome extension setup for the existing-profile bridge",
-		handler: async (_args, ctx) => {
-			const extensionPath = browserExtensionPath();
-			const proceed = await ctx.ui.confirm(
-				"Chrome bridge setup",
-				`This will open chrome://extensions and reveal the extension folder in Finder.\n\nAfter the windows open: enable Developer mode → Load unpacked → select:\n${extensionPath}\n\nPress Enter to continue, or Esc to cancel.`,
-			);
-			if (!proceed) {
-				ctx.ui.notify("Chrome bridge setup cancelled", "info");
+			const tokens = (args || "").trim().split(/\s+/).filter(Boolean);
+			if (tokens.length === 0) {
+				const picked = await ctx.ui.select("pi-chrome — what would you like to do?", [
+					"doctor — quick health check; tells you what's wrong if Chrome isn't responding",
+					"onboard — install the Chrome companion extension (first-time setup)",
+					"settings — change pi-chrome behaviour (background mode, click realism)",
+				]);
+				if (!picked) return;
+				if (picked.startsWith("doctor")) return doctorHandler(ctx);
+				if (picked.startsWith("onboard")) return onboardHandler(ctx);
+				if (picked.startsWith("settings")) return settingsHandler(ctx, []);
 				return;
 			}
-			if (process.platform === "darwin") {
-				await pi.exec("open", ["-a", "Google Chrome", "chrome://extensions"], { cwd: workspaceCwd(ctx), timeout: 5_000 }).catch(() => undefined);
-				await pi.exec("open", ["-R", extensionPath], { cwd: workspaceCwd(ctx), timeout: 5_000 }).catch(() => undefined);
-				await pi.exec("sh", ["-lc", `printf %s ${JSON.stringify(extensionPath)} | pbcopy`], { cwd: workspaceCwd(ctx), timeout: 5_000 }).catch(() => undefined);
+			const [head, ...rest] = tokens;
+			switch (head) {
+				case "doctor": return doctorHandler(ctx);
+				case "onboard": return onboardHandler(ctx);
+				case "settings": return settingsHandler(ctx, rest);
+				default:
+					ctx.ui.notify(`Unknown subcommand '${head}'. Try: /chrome doctor | onboard | settings.`, "warning");
 			}
-			ctx.ui.notify(
-				"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.11.4",
+	"version": "0.12.0",
 	"description": "Drive your existing logged-in Chrome from Pi — no re-login, no throwaway profile, watch the agent work in real time (or toggle quiet background mode).",
 	"keywords": [
 		"pi-package",