You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add support for model_reasoning_effort parameter to control thinking budget #37
Currently, the codex MCP tool only supports specifying the model parameter, but doesn't allow controlling the model_reasoning_effort configuration. This means all tasks use the same thinking budget defined in ~/.codex/config.toml, which is suboptimal for different task complexities.
Use Case
Different tasks require different levels of reasoning:
Simple tasks (e.g., "add a print statement", "fix typo"): low or medium reasoning effort is sufficient and faster
Complex tasks (e.g., "refactor architecture", "debug race condition"): high or xhigh reasoning effort provides better quality
Currently, users must either:
Manually edit ~/.codex/config.toml before each task (cumbersome)
Create multiple profiles (requires pre-configuration and doesn't scale)
Accept suboptimal performance (waste time on simple tasks or get poor results on complex ones)
Proposed Solution
Add a reasoning_effort parameter to the codex tool that maps to Codex CLI's -c model_reasoning_effort="..." option:
# Quick fix - use low reasoningmcp.call_tool("codex", {
"PROMPT": "Add error logging to line 42",
"cd": "/path/to/project",
"reasoning_effort": "low"
})
# Complex refactoring - use xhigh reasoningmcp.call_tool("codex", {
"PROMPT": "Refactor the authentication system to support OAuth2",
"cd": "/path/to/project",
"reasoning_effort": "xhigh"
})
Benefits
Performance: Faster responses for simple tasks
Quality: Better results for complex tasks
Cost efficiency: Avoid unnecessary compute on trivial operations
Flexibility: Claude Code can dynamically adjust reasoning budget based on task complexity
Additional Context
The Codex CLI already supports this via -c model_reasoning_effort="...". This feature request simply exposes that capability through the MCP interface, similar to how the model parameter is already exposed.
Activity
feat: add reasoning_effort parameter to control thinking budget