Codex CLI repeatedly reports bundled node_repl MCP startup failure on macOS

Summary

Codex CLI on macOS repeatedly prints a startup failure for the bundled node_repl MCP client:

⚠ MCP client for `node_repl` failed to start: MCP startup failed: No such file or directory (os error 2)
⚠ MCP startup incomplete (failed: node_repl)

The session otherwise starts and remains usable, but node_repl is unavailable and the warning recurs.

Environment

• macOS 26.5.2
• Codex CLI 0.144.1
• Terminal: iTerm2
• Working directory: local Xcode/Swift project
• Shell: zsh

Expected behavior

The bundled node_repl MCP client should either:

1. start successfully without requiring a manual external path/configuration, or
2. remain disabled without emitting a repeated startup failure when its executable/runtime is not present.

If an external dependency is required, the error should identify the missing executable or path and provide an actionable remediation.

Actual behavior

Codex reports only No such file or directory (os error 2), without identifying which file or executable is missing.

Related issue

Possibly related to #31533, although that report concerns Codex Desktop tool exposure, while this report is the Codex terminal CLI failing during MCP startup.