fix: auto-detect codex version and use correct MCP command #41
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes compatibility issues with codex versions 0.43.0-alpha.5 and later by automatically detecting the installed codex version and using the correct MCP subcommand.
Problem
Starting from codex version 0.43.0-alpha.5, OpenAI introduced a new
mcp-serversubcommand to replace the oldermcpcommand for running Codex as an MCP server. This change broke compatibility for users upgrading to newer versions, causing connection errors like "MCP error -32000: Connection closed" (#39).Solution
This PR adds automatic version detection that:
codex --versionmcp-serverfor versions >= 0.43.0-alpha.5mcpfor older versions (< 0.43.0-alpha.5)mcp-serverif version detection fails (assumes newer installation)Testing
mcp)mcp)mcp)mcp-server)mcp-server)mcp-server)Changes
getCodexMcpCommand()function insrc/codex/codexMcpClient.tsconnect()methodFixes
🤖 Generated with Claude Code
via Happy