Codex currently does not support statefulMode: stateful

Resolved 💬 1 comment Opened Nov 13, 2025 by wangguchen Closed Jan 10, 2026

What feature would you like to see?

Problem
The MCP (Model Context Protocol) functionality in Codex currently does not support statefulMode: stateful. It only works with statefulMode: stateless, which limits the ability to maintain conversation context across multiple interactions.

Current Behavior
MCP integration only functions properly when configured with statefulMode: stateless
Attempting to use statefulMode: stateful results in incompatibility issues
Expected Behavior
MCP functionality should support both stateful and stateless modes to allow users to:

Maintain conversation context across multiple requests
Preserve state information for more coherent multi-turn interactions
Have flexibility in choosing the appropriate mode for their use case
Configuration Example
javascript

// Currently only this works:
{
statefulMode: "stateless"
}

// This should also be supported:
{
statefulMode: "stateful"
}
Impact
This limitation affects users who need persistent context in their MCP-based workflows, requiring them to work around the stateless constraint.

Additional information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗