[Bug]: Official Codex plugin fails with spawn codex ENOENT on Windows

[tcflying]

Version / 版本号

MiniMax Code Desktop 3.0.67.129; official Codex plugin 0.2.4 from the cn-prod target published on 2026-08-21; Codex CLI 0.147.0.

Platform / 平台

Windows

OS version / 系统版本

Windows 11 Pro, build 10.0.26200, x64.

Issue area / 问题类型

MCP / OAuth / integration

Upload ID / 日志上传 ID

Not uploaded. The minimal sanitized log and deterministic reproduction are included below.

What happened? / 问题描述

The official Codex plugin is enabled, but its codex-local MCP server cannot start on Windows. The plugin proxy launches spawn("codex", ["mcp-server"]); Node's Windows process resolution does not execute the npm codex.cmd shim in this context, so MiniMax Code repeatedly reports spawn codex ENOENT even though codex --version works in an interactive shell.

The official content-addressed plugin cache was not modified while diagnosing or working around this issue.

Steps to reproduce / 复现步骤

1. Install MiniMax Code Desktop 3.0.67.129 on Windows.
2. Install and authenticate the official Codex CLI (codex-cli 0.147.0 in this reproduction).
3. Enable the official Codex plugin 0.2.4 in MiniMax Code.
4. Restart MiniMax Code and let it load runtime skills or invoke the Codex integration.
5. Inspect the MiniMax main log.

Expected behavior / 预期行为

The official plugin should resolve the installed Codex CLI on Windows and start codex mcp-server, exposing the codex and codex-reply MCP tools.

Actual behavior / 实际行为

MiniMax Code retries the integration and logs:

[mcp:codex-local:stderr] codex proxy error: spawn codex ENOENT
[OFFICIAL] Plugin MCP tools/list failed {"pluginName":"codex","serverName":"codex-local","errorType":"Error"}

The error repeated approximately every five minutes. Running the native Codex executable directly with mcp-server succeeds: JSON-RPC initialize, tools/list, and a deterministic read-only tools/call all pass, and tools/list exposes codex and codex-reply.

As a local diagnostic workaround, placing a native codex.exe launcher in %USERPROFILE%\.minimax\bin (already first in MiniMax Code's inherited user PATH) and fully restarting MiniMax Code makes the unchanged official proxy connect successfully:

Connected MCP server {"serverName":"codex-local","connectionKey":"codex-local","transportType":"stdio"}

After the restart boundary there are no new spawn codex ENOENT or Plugin MCP tools/list failed entries. This isolates the failure to Windows resolution of the bare codex command, not authentication or the Codex MCP protocol.

Suggested fix

Please make the official proxy resolve the Windows Codex launcher explicitly. Possible options include resolving the native executable from the installed Codex package, invoking codex.cmd through a Windows-aware launcher, or using a cross-platform command resolver. The fix should preserve stdio, working directory, environment, exit status, and arguments.

Equivalent Windows raw-spawn reports in the upstream Codex ecosystem:

• spawn() in app-server.mjs fails with ENOENT on Windows openai/codex-plugin-cc#53
• Windows: spawn("codex") in app-server.mjs throws ENOENT (Node does not try PATHEXT for .cmd shims) openai/codex-plugin-cc#287
• Windows: spawn ENOENT in app-server.mjs — missing shell:true for .cmd shims openai/codex#16337

I searched the MiniMax Code issue tracker for codex, codex-local, spawn codex, ENOENT, and Windows variants before preparing this report and found no equivalent issue.