@minhspark/codex-mcp-bridge 1.11.2 → 1.11.3

package/CHANGELOG.md

@@ -2,10 +2,22 @@
 
 Follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and [SemVer](https://semver.org/).
 
-## [Unreleased]
+## [1.11.3] - 2026-09-03
 
 ### Fixed
 
+- **The peer endpoint never started on Windows, so the bridge was one-way there.** `/tmp/cc-socks` has no
+  Windows equivalent, and `path.join` rewrote it to `\tmp\cc-socks` on the system drive, where `listen()`
+  fails with `EACCES`. Codex could push a message into a live Claude session, but Claude had no address to
+  answer on - and the only sign was one line on stderr saying replies could not be received, which nothing
+  surfaces once the server is running under an MCP client. The peer now listens on a named pipe on Windows,
+  the same transport Claude Code itself advertises in `~/.claude/sessions/<pid>.json`, and skips the
+  directory, mode and unlink steps that a pipe does not have.
+
+- `fast-uri` is bumped to 3.1.7 and `qs` to 6.16.0. `fast-uri` 3.0.0-3.1.5 is vulnerable to host confusion
+  and server-side request forgery through repeated hostname percent-decoding (CVE-2026-75899, high); it
+  reaches the tree transitively through `@modelcontextprotocol/sdk` -> `ajv`.
+
 - **A tag is not a release, and nothing was creating the release.** Pushing `v1.10.1`, `v1.11.0` and
   `v1.11.1` published all three to npm, while the Releases page still showed `v1.10.0` as *Latest* -
   the one release that had been created by hand. Anyone reading the repository saw a project that had

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@minhspark/codex-mcp-bridge",
-  "version": "1.11.2",
+  "version": "1.11.3",
   "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/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.2";
+const VERSION = "1.11.3";
 const FORWARD_MIN_INTERVAL_MS = 5000;
 const FORWARD_MAX_PER_SESSION = 50;
 

package/src/index.mjs

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

package/src/peer-protocol.mjs

@@ -5,9 +5,24 @@ import net from "node:net";
 import os from "node:os";
 import path from "node:path";
 
-import { homeDir } from "./platform.mjs";
+import { homeDir, IS_WINDOWS } from "./platform.mjs";
 
 const SOCKET_DIR = "/tmp/cc-socks";
+
+/**
+ * Windows has no /tmp, and path.join rewrites the unix default to "\tmp\cc-socks"
+ * on the system drive, where listen() fails with EACCES. The endpoint then never
+ * comes up, so Claude has no address to answer on and the bridge is silently
+ * one-way: messages reach Claude, replies never come back.
+ *
+ * Claude Code advertises a named pipe on Windows for exactly this reason, so the
+ * peer uses the same transport there. net.connect({ path }) and server.listen()
+ * accept a pipe name unchanged, so only creation differs - a pipe has no
+ * directory to create, no mode to chmod and no file to unlink beforehand.
+ */
+function peerSocketPath(pid) {
+  return IS_WINDOWS ? `\\\\.\\pipe\\LOCAL\\cc-peer-${pid}` : path.join(SOCKET_DIR, `${pid}.sock`);
+}
 const PEER_PROTOCOL_VERSION = 1;
 const CLAUDE_VERSION_HINT = "2.1.229";
 const PS_BIN = "/bin/ps";
@@ -171,7 +186,7 @@ export class PeerEndpoint {
     this.cwd = cwd;
     this.log = log;
     this.pid = process.pid;
-    this.socketPath = path.join(SOCKET_DIR, `${this.pid}.sock`);
+    this.socketPath = peerSocketPath(this.pid);
     this.registryPath = path.join(sessionsDir(), `${this.pid}.json`);
     this.keyPath = null;
     this.server = null;
@@ -219,16 +234,16 @@ export class PeerEndpoint {
     const keyHash = crypto.createHash("sha256").update(`${peerToken}${procStart}`).digest("hex");
     this.keyPath = path.join(sessionsDir(), `${this.pid}.${keyHash}.key`);
 
-    fs.mkdirSync(SOCKET_DIR, { recursive: true });
+    if (!IS_WINDOWS) fs.mkdirSync(SOCKET_DIR, { recursive: true });
     fs.mkdirSync(sessionsDir(), { recursive: true });
-    if (fs.existsSync(this.socketPath)) fs.rmSync(this.socketPath, { force: true });
+    if (!IS_WINDOWS && fs.existsSync(this.socketPath)) fs.rmSync(this.socketPath, { force: true });
 
     await new Promise((resolve, reject) => {
       this.server = net.createServer((socket) => this.#handleConnection(socket));
       this.server.on("error", reject);
       this.server.listen(this.socketPath, resolve);
     });
-    fs.chmodSync(this.socketPath, 0o600);
+    if (!IS_WINDOWS) fs.chmodSync(this.socketPath, 0o600);
 
     this.registry = {
       pid: this.pid,