@minhspark/codex-mcp-bridge 1.11.0 → 1.11.1

package/CHANGELOG.md

@@ -2,6 +2,31 @@
 
 Follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and [SemVer](https://semver.org/).
 
+## [1.11.1] - 2026-08-23
+
+### Fixed
+
+- **Re-running `codex-mcp-bridge-install` deleted settings it does not write.** It assigned a whole new
+  entry over the old one, so `CODEX_BRIDGE_ALLOWED_THREADS`, a hand-added `CODEX_BRIDGE_THREAD_POLICY`
+  and any key from a later version were dropped, and `CODEX_BRIDGE_ALLOWED_ROOTS` was reset to the
+  install directory. Upgrading is exactly when people re-run it, so the command you reach for to keep
+  the bridge current was the command that silently broke it. Measured on a config carrying four custom
+  values: all four gone, roots narrowed from two projects to the install directory, other MCP servers
+  untouched.
+
+  Existing values are now the fallback rather than the casualty. Precedence, highest first: a variable
+  passed to this run, what the config already says, then the default. `command`, `args` and `CODEX_BIN`
+  are still resolved fresh — pointing the entry at the code installed now is the reason to re-run at
+  all. `--reset` discards inherited values for the rare case of wanting the defaults back.
+
+### Added
+
+- The installer now writes `CODEX_BRIDGE_THREAD_POLICY` explicitly, and when it is left at `owned` it
+  says what that means: a thread opened in the Codex app or the VS Code extension will answer
+  `NOT AUTHORIZED`, because its id is assigned as it opens and cannot be allowlisted in advance. Shipping
+  1.11.0 without this left the fix reachable only by reading the environment table — and the symptom
+  points nowhere near the setting responsible.
+
 ## [1.11.0] - 2026-08-23
 
 ### Added

package/README.md

@@ -88,6 +88,16 @@ npm install -g git+https://github.com/buidangminh23/codex-mcp-bridge.git
 
 Either route puts four commands on your PATH — `codex-mcp-bridge` and `claude-mcp-bridge` are the two servers, `codex-mcp-bridge-install` and `claude-mcp-bridge-install` do the wiring in the steps below. Wherever this README runs `node scripts/install-claude-desktop.mjs`, an installed copy runs `codex-mcp-bridge-install` instead.
 
+#### Upgrading an install you already have
+
+```bash
+npm install -g @minhspark/codex-mcp-bridge@latest
+```
+
+Then restart Claude Desktop or Claude Code — an MCP server only loads its code when the client spawns it. Check `codex_bridge_status` reports the version you expect. The config needs no edit: the global install path carries no version number, so the entry keeps pointing at the right file.
+
+Re-running `codex-mcp-bridge-install` is **not** required to upgrade, and before 1.11.1 it actively hurt: it replaced the whole entry, discarding `CODEX_BRIDGE_ALLOWED_THREADS`, any hand-added `CODEX_BRIDGE_THREAD_POLICY`, and resetting `CODEX_BRIDGE_ALLOWED_ROOTS` to the install directory. From 1.11.1 it keeps what is already there — an environment variable you pass wins, the existing value is the fallback, and `--reset` gives you the defaults back.
+
 **Clone it** — right if you intend to read, test or change the code:
 
 ```bash
@@ -96,6 +106,8 @@ cd codex-mcp-bridge
 npm install
 ```
 
+A clone upgrades with `git pull && npm ci`, then the same restart.
+
 Confirm the tree is healthy before wiring it into anything:
 
 ```bash

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@minhspark/codex-mcp-bridge",
-  "version": "1.11.0",
+  "version": "1.11.1",
   "description": "Two-way MCP bridge between Claude and Codex: prompts into a live Codex thread, messages into a running Claude Code session.",
   "keywords": [
     "mcp",

package/scripts/install-claude-desktop.mjs

@@ -7,6 +7,7 @@ import { PLATFORM_LABEL, claudeDesktopConfigPath, resolveCodexBin } from "../src
 
 const root = path.resolve(path.dirname(fileURLToPath(import.meta.url)), "..");
 const cfgPath = process.env.CLAUDE_DESKTOP_CONFIG ?? claudeDesktopConfigPath();
+const reset = process.argv.includes("--reset");
 
 /**
  * When the package is installed as a dependency its own directory is never a
@@ -31,16 +32,55 @@ fs.mkdirSync(path.dirname(cfgPath), { recursive: true });
 
 const cfg = fs.existsSync(cfgPath) ? JSON.parse(fs.readFileSync(cfgPath, "utf8")) : {};
 cfg.mcpServers = cfg.mcpServers ?? {};
+
+/**
+ * Re-running the installer used to assign a whole new entry over the old one,
+ * which silently deleted every setting the installer does not itself write -
+ * CODEX_BRIDGE_ALLOWED_THREADS and a hand-added CODEX_BRIDGE_THREAD_POLICY
+ * among them - and reset CODEX_BRIDGE_ALLOWED_ROOTS back to the install
+ * directory. Upgrading is the moment people re-run this, so the command they
+ * reach for to keep the bridge current was the command that broke it.
+ *
+ * Existing values are now the fallback rather than the casualty. Precedence,
+ * highest first: an environment variable passed to this run, what the config
+ * already says, then the default. `--reset` drops the middle one for the rare
+ * case of wanting the defaults back.
+ */
+const previousEnv = (reset ? {} : cfg.mcpServers["codex-bridge"]?.env) ?? {};
+const settled = (name, fallback) => process.env[name] ?? previousEnv[name] ?? fallback;
+
+const kept = Object.keys(previousEnv).filter(
+  (name) => process.env[name] === undefined && name !== "CODEX_BIN",
+);
+
 cfg.mcpServers["codex-bridge"] = {
   command: nodeBin,
   args: [path.join(root, "src", "index.mjs")],
   env: {
+    /**
+     * Keys this installer knows nothing about survive too - a setting added by
+     * a later version, or by hand, is not this script's to throw away.
+     */
+    ...previousEnv,
+    /**
+     * These three are the point of re-running: they name where the code and
+     * the codex binary actually live now, so they are resolved fresh rather
+     * than inherited.
+     */
     CODEX_BIN: codexBin,
-    CODEX_APP_SERVER_URL: process.env.CODEX_APP_SERVER_URL ?? "ws://127.0.0.1:8791",
-    CODEX_BRIDGE_ALLOWED_ROOTS: process.env.CODEX_BRIDGE_ALLOWED_ROOTS ?? defaultRoots,
-    CODEX_BRIDGE_APPROVAL: process.env.CODEX_BRIDGE_APPROVAL ?? "deny",
-    CODEX_BRIDGE_APPROVAL_POLICY: process.env.CODEX_BRIDGE_APPROVAL_POLICY ?? "on-request",
-    CODEX_BRIDGE_SANDBOX: process.env.CODEX_BRIDGE_SANDBOX ?? "workspace-write",
+    CODEX_APP_SERVER_URL: settled("CODEX_APP_SERVER_URL", "ws://127.0.0.1:8791"),
+    CODEX_BRIDGE_ALLOWED_ROOTS: settled("CODEX_BRIDGE_ALLOWED_ROOTS", defaultRoots),
+    CODEX_BRIDGE_APPROVAL: settled("CODEX_BRIDGE_APPROVAL", "deny"),
+    CODEX_BRIDGE_APPROVAL_POLICY: settled("CODEX_BRIDGE_APPROVAL_POLICY", "on-request"),
+    /**
+     * Written out even at its default so it is visible in the file. Left
+     * implicit, the one setting that decides whether the bridge can reach a
+     * thread a human opened is a variable you have to already know exists -
+     * and the symptom when you do not, every thread answering NOT AUTHORIZED,
+     * points nowhere near it.
+     */
+    CODEX_BRIDGE_THREAD_POLICY: settled("CODEX_BRIDGE_THREAD_POLICY", "owned"),
+    CODEX_BRIDGE_SANDBOX: settled("CODEX_BRIDGE_SANDBOX", "workspace-write"),
     ...(process.env.CODEX_BRIDGE_MODEL ? { CODEX_BRIDGE_MODEL: process.env.CODEX_BRIDGE_MODEL } : {}),
     ...(process.env.CODEX_BRIDGE_EFFORT ? { CODEX_BRIDGE_EFFORT: process.env.CODEX_BRIDGE_EFFORT } : {}),
   },
@@ -55,6 +95,14 @@ fs.writeFileSync(cfgPath, `${JSON.stringify(cfg, null, 2)}\n`, "utf8");
 console.log(`platform: ${PLATFORM_LABEL}`);
 console.log(`updated ${cfgPath}`);
 console.log(JSON.stringify(cfg.mcpServers["codex-bridge"], null, 2));
+
+if (reset) {
+  console.log("\n--reset: existing values were discarded in favour of the defaults.");
+} else if (kept.length) {
+  console.log(`\nkept from the existing entry: ${kept.join(", ")}`);
+  console.log("Pass the variable to override one, or --reset to drop them all.");
+}
+
 const writtenRoots = cfg.mcpServers["codex-bridge"].env.CODEX_BRIDGE_ALLOWED_ROOTS;
 if (writtenRoots.split(path.delimiter).some((entry) => entry.split(path.sep).includes("node_modules"))) {
   console.log(
@@ -64,4 +112,14 @@ if (writtenRoots.split(path.delimiter).some((entry) => entry.split(path.sep).inc
   );
 }
 
+if (cfg.mcpServers["codex-bridge"].env.CODEX_BRIDGE_THREAD_POLICY === "owned") {
+  console.log(
+    "\nNOTE: thread policy is `owned` - this bridge may only act on threads it created itself.\n" +
+      "A thread you open in the Codex app or the VS Code extension will answer NOT AUTHORIZED,\n" +
+      "because its id is assigned as it opens and cannot be allowlisted in advance. To let the\n" +
+      "bridge reach any thread working inside CODEX_BRIDGE_ALLOWED_ROOTS, re-run with:\n" +
+      "  CODEX_BRIDGE_THREAD_POLICY=roots codex-mcp-bridge-install",
+  );
+}
+
 console.log("\nRestart Claude Desktop to load the bridge.");

package/src/claude-bridge.mjs

@@ -8,7 +8,7 @@ import { PLATFORM_LABEL } from "./platform.mjs";
 import { PeerEndpoint, findClaudeSession, listClaudeSessions, readTranscript } from "./peer-protocol.mjs";
 import { runTurn } from "./turn.mjs";
 
-const VERSION = "1.11.0";
+const VERSION = "1.11.1";
 const FORWARD_MIN_INTERVAL_MS = 5000;
 const FORWARD_MAX_PER_SESSION = 50;
 

package/src/index.mjs

@@ -19,7 +19,7 @@ import {
 import { runTurn } from "./turn.mjs";
 import { BridgeSecurityPolicy } from "./security-policy.mjs";
 
-const VERSION = "1.11.0";
+const VERSION = "1.11.1";
 const log = (msg) => process.stderr.write(`[codex-mcp-bridge] ${msg}\n`);
 
 /**