MCP server stdio command path resolution uses wrong bundle path when app is installed as ChatGPT.app
Description
When Codex is installed on macOS via the App Store (as ChatGPT.app), the MCP server resolves stdio command paths using Codex.app as the bundle signing base name, causing ENOENT errors.
Steps to Reproduce
- Install Codex from the App Store (gets installed as
ChatGPT.app). - Observe MCP configuration warnings in the UI:
````
⚠ mcp MCP configuration has optional issues — Set the missing MCP env vars or disable the affected server.
configured servers 2
disabled servers 0
stdio servers 2
node_repl stdio command "/Applications/Codex.app/Contents/Resources/cua_node/bin/node_repl" is not resolvable (No such file or directory (os error 2))
computer-use stdio command "./Codex Computer Use.app/Contents/SharedSupport/SkyComputerUseClient.app/Contents/MacOS/SkyComputerUseClient" is not resolvable (No such file or directory (os error 2))
Expected Behavior
MCP server path resolution should use the actual bundle name (ChatGPT.app) instead of assuming Codex.app.
Actual Behavior
MCP tries to find binary paths at:
/Applications/Codex.app/Contents/Resources/cua_node/bin/node_repl./Codex Computer Use.app/...
when the actual installation is at /Applications/ChatGPT.app.
Workaround
Creating a symlink works:
ln -s /Applications/ChatGPT.app /Applications/Codex.app
Environment
- Codex CLI version: 0.144.0-alpha.4
- macOS version: 26.5.2 (Sequoia)
- Installation method: App Store (ChatGPT.app)
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗