codex mcp-server cannot resume conversation with ID #8726
Description
What version of Codex is running?
0.77
What subscription do you have?
Plus
Which model were you using?
gpt-5.2-codex
What platform is your computer?
Darwin 25.2.0 arm64 arm
What issue are you seeing?
The docs here show:
- Conversations
newConversation→ start a Codex sessionsendUserMessage/sendUserTurn→ send user input into a conversationinterruptConversation→ stop the current turnlistConversations,resumeConversation,archiveConversation
however through codex as an mcp server, you cannot continue a conversation using a conversation id. Even if you went into /.codex and found the ids, you couldn't pass them in to continue a conversation.
called codex-reply via MCP with the conversation id
019b8c02-92aa-7ac1-acc3-ec39a218a3d4.
Result (from the MCP server):
Session not found for conversation_id: 019b8c02-92aa-7ac1-acc3-
ec39a218a3d4
Codex suggested fix:
- Extend the MCP request surface
The CLI MCP server only accepts standard MCP methods + tools/list + tools/
call.
So you’d need to add new request variants in codex-rs/mcp-types (the
ClientRequest enum) for:
- listConversations
- resumeConversation
- (optionally archiveConversation)
-
Implement handlers in the MCP server
In codex-rs/mcp-server/src/message_processor.rs, add handlers for those
new request types. -
Reuse the conversation manager from app‑server
The MCP server already creates a ConversationManager (see
message_processor.rs).
You’d wire the new methods to:
- conversation_manager.list_conversations()
- conversation_manager.resume_conversation(conversation_id)
What steps can reproduce the bug?
Get a conversation id
Use codex as mcp server to get a reply
What is the expected behavior?
Provide a conversation id to continue a conversation
Additional information
No response