ghost-bridge 0.8.0 → 0.9.1

package/README.md

@@ -16,6 +16,7 @@ Most browser-capable AI tools start a separate browser. Ghost Bridge connects AI
 - Inspect page structure, text, screenshots, errors, and network traffic
 - Search and extract script sources, even in production bundles
 - Click, type, scroll, and submit forms on the current page
+- Bind multiple Chrome tabs as named targets and operate them independently
 - Share one Chrome transport across multiple MCP clients
 
 ## Quick Start
@@ -94,6 +95,9 @@ Typical prompts:
 | `get_page_content` | Text, HTML, and structured DOM extraction |
 | `get_interactive_snapshot` | Find clickable and editable elements |
 | `dispatch_action` | Click, fill, press, scroll, hover, select |
+| `bind_tab` | Bind a Chrome tab as a named target such as `cases` or `app` |
+| `unbind_tab` | Remove a named target binding |
+| `list_targets` | Show named targets and their per-tab session status |
 | `pin_current_tab` | Keep Ghost Bridge attached to the current tab while you browse elsewhere |
 | `pin_tab` | Pin a target tab by tab ID, URL fragment, or title fragment |
 | `unpin_tab` | Return to following the focused tab |
@@ -117,9 +121,19 @@ Recommended flow:
 
 Notes:
 
+- Use `bind_tab` when a workflow spans multiple pages. For example, bind a checklist page as `cases` and a business page as `app`, then call tools with `target: "cases"` or `target: "app"`.
+- All browser tools accept an optional `target` parameter. When named targets are bound, `dispatch_action` requires `target` so refs from one page are not accidentally used on another page.
 - Use `pin_current_tab` when you are debugging a page and need to switch to other tabs without changing the AI target. Use `unpin_tab` to restore the original follow-focused-tab behavior.
 - `list_network_requests` and `get_network_detail` automatically summarize `data:` URLs and very long URLs so inline images or oversized query strings do not overwhelm model context
 
+Multi-page example:
+
+```text
+Bind the current checklist tab as cases.
+Bind the tab whose title contains "Orders" as app.
+Read the next case from target cases, operate target app, then mark the case passed or failed back on target cases.
+```
+
 ## Configuration
 
 | Setting | Default | Notes |
@@ -133,18 +147,26 @@ Notes:
 ```mermaid
 flowchart LR
     A["AI Client<br/>Claude / Codex / Cursor"]
-    B["Ghost Bridge MCP Server<br/>server.js"]
+    S["Session Process<br/>dist/server.js (stdio)"]
+    B["Ghost Bridge Daemon<br/>resident WebSocket service"]
     C["Chrome Extension<br/>background.js"]
-    D["Browser Tab<br/>Target Context"]
+    D["Browser Tabs<br/>Target Sessions"]
 
-    A <-->|"stdio"| B
-    B <-->|"WebSocket"| C
+    A <-->|"stdio"| S
+    S <-->|"WebSocket (mcp-client)"| B
+    C <-->|"WebSocket"| B
     C <-->|"CDP"| D
 ```
 
+The WebSocket service runs as a detached daemon, independent of any MCP session:
+
+- The first session process spawns the daemon automatically; it keeps running after that session exits
+- If the daemon crashes, any live session detects it and respawns it automatically
+- Stop it manually with `ghost-bridge stop` (close live MCP sessions first, otherwise they will bring it back on their next reconnect)
+
 ## Troubleshooting
 
-If the popup shows `No Bridge` / `Not Found`, it means the Chrome extension could not find a Ghost Bridge WebSocket service on the configured port. It does not necessarily mean your AI client is closed.
+If the popup shows `No Bridge` / `Not Found`, it means the Chrome extension could not find a Ghost Bridge WebSocket service on the configured port. With the resident daemon this normally only happens before the first MCP session of the day starts, or after `ghost-bridge stop`. Starting any MCP session (or reconnecting the extension) brings the service back within seconds.
 
 Run `ghost-bridge status` and check:
 

package/dist/cli.js

@@ -6010,6 +6010,7 @@ init_source();
 import { fileURLToPath as fileURLToPath2 } from "url";
 import path5 from "path";
 import fs5 from "fs";
+import os7 from "os";
 var __filename = fileURLToPath2(import.meta.url);
 var __dirname = path5.dirname(__filename);
 var packageJsonParams = JSON.parse(
@@ -6062,4 +6063,62 @@ program2.command("status").description("Check Ghost Bridge configuration status"
     console.error(source_default.red("Error checking status:"), error);
   }
 });
+var sleepMs = (ms) => new Promise((resolve) => setTimeout(resolve, ms));
+function isProcessAlive(pid) {
+  try {
+    process.kill(pid, 0);
+    return true;
+  } catch (e) {
+    return e.code === "EPERM";
+  }
+}
+function readPortInfoFile() {
+  const portInfoFile = process.env.GHOST_BRIDGE_PORT_INFO || path5.join(os7.tmpdir(), "ghost-bridge-port.json");
+  if (!fs5.existsSync(portInfoFile)) return null;
+  try {
+    const info = JSON.parse(fs5.readFileSync(portInfoFile, "utf-8"));
+    return info && info.pid ? { file: portInfoFile, ...info } : null;
+  } catch {
+    return null;
+  }
+}
+function removePortInfoFile(entry) {
+  try {
+    const current = JSON.parse(fs5.readFileSync(entry.file, "utf-8"));
+    if (current.pid === entry.pid) fs5.unlinkSync(entry.file);
+  } catch {
+  }
+}
+program2.command("stop").description("Stop the resident ghost-bridge daemon").action(async () => {
+  try {
+    const entry = readPortInfoFile();
+    if (!entry) {
+      console.log(source_default.yellow("\u672A\u53D1\u73B0\u8FD0\u884C\u4E2D\u7684 ghost-bridge \u5E38\u9A7B\u670D\u52A1"));
+      return;
+    }
+    if (!isProcessAlive(entry.pid)) {
+      removePortInfoFile(entry);
+      console.log(source_default.yellow(`\u7AEF\u53E3\u4FE1\u606F\u5DF2\u8FC7\u671F\uFF08PID ${entry.pid} \u4E0D\u5B58\u5728\uFF09\uFF0C\u5DF2\u6E05\u7406`));
+      return;
+    }
+    console.log(source_default.blue(`\u6B63\u5728\u505C\u6B62 ghost-bridge \u5E38\u9A7B\u670D\u52A1 (PID: ${entry.pid})...`));
+    process.kill(entry.pid, "SIGTERM");
+    const deadline = Date.now() + 5e3;
+    while (Date.now() < deadline && isProcessAlive(entry.pid)) {
+      await sleepMs(200);
+    }
+    if (isProcessAlive(entry.pid)) {
+      console.error(source_default.red("\u670D\u52A1\u672A\u80FD\u5728\u9884\u671F\u65F6\u95F4\u5185\u9000\u51FA\uFF0C\u8BF7\u624B\u52A8\u68C0\u67E5\u8BE5\u8FDB\u7A0B"));
+      process.exit(1);
+    }
+    removePortInfoFile(entry);
+    console.log(source_default.green("\u2705 ghost-bridge \u5E38\u9A7B\u670D\u52A1\u5DF2\u505C\u6B62"));
+    console.log(
+      source_default.dim("\u6CE8\u610F\uFF1A\u82E5\u4ECD\u6709\u6D3B\u8DC3\u7684 MCP \u4F1A\u8BDD\uFF0C\u4F1A\u8BDD\u4F1A\u5728\u4E0B\u6B21\u91CD\u8FDE\u65F6\u81EA\u52A8\u91CD\u65B0\u62C9\u8D77\u670D\u52A1\uFF1B\u5982\u9700\u5F7B\u5E95\u505C\u6B62\uFF0C\u8BF7\u5148\u5173\u95ED\u4F7F\u7528\u4E2D\u7684\u4F1A\u8BDD\u3002")
+    );
+  } catch (error) {
+    console.error(source_default.red("Error stopping ghost-bridge:"), error);
+    process.exit(1);
+  }
+});
 program2.parse();