codex-control-chrome-mcp 1.4.0 → 1.4.2

package/CHANGELOG.md

@@ -6,6 +6,18 @@ This project follows semantic versioning.
 
 ## [Unreleased]
 
+## [1.4.2] - 2026-11-11
+
+### Fixed
+
+- `attach` now carries `networkPolicy: { constraints: [] }`. Extension 1.26.1102.11740 passes `e.networkPolicy` to `ar.getInstance().attach(tabId, e.networkPolicy)`, and that installer reads `options.timeoutMs` before any validation, so a request without the field threw `Cannot read properties of undefined (reading 'timeoutMs')` and the debugger never attached. Every CDP tool (`chrome_navigate`, `chrome_evaluate`, `chrome_screenshot`, `chrome_cdp_send`, `chrome_attach_tab`) failed on it. Empty constraints normalize to `defaultAction: "allow"` with no rules, and the installer returns before touching declarativeNetRequest, so the field adds no policy side effect. Verified against the live extension: plain `attach` fails, `attach` with the empty policy succeeds, `Page.navigate` and `Runtime.evaluate` run.
+
+## [1.4.1] - 2026-07-04
+
+### Fixed
+
+- The self-heal now recognizes every string the extension uses for a lost debugger attachment, not just Chrome's `Debugger is not attached`. A concurrency race soak (`scripts/concurrency-check.mjs --inject-detach`, which detaches a tab mid-command) surfaced two more that were slipping through unhealed: `Debugger unattached` (the extension's own `se`-map check) and `Detached while handling command.` (detached mid-command). `isNotAttachedError` now matches all three, so `withSession` recovers them too. Under the race soak this took unrecovered "not attached" failures from a handful to zero.
+
 ## [1.4.0] - 2026-07-04
 
 ### Changed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codex-control-chrome-mcp",
-  "version": "1.4.0",
+  "version": "1.4.2",
   "description": "MCP server and native host bridge for controlling Chrome through the Codex Chrome extension.",
   "license": "MIT",
   "type": "module",

package/src/mcp-server.js

@@ -347,7 +347,13 @@ export function registerTools(server, runtime) {
  * doubles as a liveness probe that surfaces a stale attach as "not attached".
  */
 async function ensureAttached(runtime, tabId) {
-  await runtime.request("attach", { tabId });
+  // The extension's attach handler passes `networkPolicy` straight to its
+  // declarativeNetRequest policy installer, which reads `options.timeoutMs`
+  // before checking anything. Omitting the field throws a TypeError and the
+  // attach never happens. Empty constraints normalize to defaultAction "allow"
+  // with no rules, which the installer returns from without installing
+  // anything, so this keeps the request free of side effects.
+  await runtime.request("attach", { tabId, networkPolicy: { constraints: [] } });
   try {
     await executeCdp(runtime, {
       tabId,
@@ -400,8 +406,13 @@ export async function withSession(runtime, tabId, run) {
   }
 }
 
+// The extension surfaces a lost debugger attachment with several distinct
+// strings, all of which are recoverable by a detach + re-attach:
+//   - "Debugger is not attached to the tab with id: N"  (Chrome, via sendCommand)
+//   - "Debugger unattached"                             (extension's own se-check)
+//   - "Detached while handling command."                (detached mid-command)
 export function isNotAttachedError(error) {
-  return /not attached/i.test(error?.message ?? String(error ?? ""));
+  return /not attached|unattached|detached while/i.test(error?.message ?? String(error ?? ""));
 }
 
 async function executeCdp(runtime, { tabId, method, params = {}, timeoutMs }) {