Description
In the Codex interface in the ChatGPT Windows app, I can successfully send the first message in a new conversation and Codex responds normally.
After the first response completes, I can type a second message, but I cannot submit it at all. The second message never gets sent.
This happens consistently and makes multi-turn Codex conversations unusable.
Steps to reproduce
- Open Codex in the ChatGPT Windows app.
- Create a new conversation.
- Send "Hello 1".
- Wait until Codex finishes responding.
- Type "Hello 2".
- Try to submit the message.
Expected behavior
"Hello 2" should be submitted and Codex should start the second turn.
Actual behavior
The first turn works normally.
After it completes, the second message can be typed into the composer, but it cannot be submitted.
The issue reproduces consistently in new conversations.
Troubleshooting already performed
- Confirmed ChatGPT is updated to the latest version available to me.
- Used Windows "Repair" for the ChatGPT app.
- This temporarily restored functionality once, but the problem returned immediately on the next follow-up message.
- Completely uninstalled and reinstalled ChatGPT.
- Created a completely fresh local Codex profile by renaming
%LOCALAPPDATA%\Codex and allowing the app to create a new one.
- Reproduced the issue again with the fresh profile.
- General ChatGPT/API connectivity appears functional.
None of these steps resolved the issue.
Relevant diagnostic logs
Around the failure, the diagnostic logs contain:
Received turn/started for unknown conversation
followed by:
Received turn/completed for unknown conversation
The logs also showed a state where a thread was considered streaming without an active runtime.
This appears consistent with the UI/client losing synchronization with the conversation/turn state.
Feedback session ID
01a0da5b-c655-7101-b016-13bf39f9a3a9
This Feedback report was submitted from the affected Codex Windows client with diagnostic logs enabled.
Environment
- OS: Windows 11
- Windows build: 10.0.26200
- ChatGPT app version reported in diagnostics: 26.917.71314
- Electron / Chrome: 153.0.8010.53
- Node: 24.19.0
- Locale: ru-RU
- CPU: AMD Ryzen 7 7800X3D
- RAM: 32 GB
- GPU: NVIDIA GeForce RTX 5070
Additional information
OpenAI Support asked me to file this GitHub issue and include the Feedback session ID and the "unknown conversation" log entries.
I was also asked to test Codex web at chatgpt.com/codex, but while signed into the same account that URL only shows/redirects me to the ChatGPT desktop app download page, so I cannot currently compare the behavior with Codex web.
Description
In the Codex interface in the ChatGPT Windows app, I can successfully send the first message in a new conversation and Codex responds normally.
After the first response completes, I can type a second message, but I cannot submit it at all. The second message never gets sent.
This happens consistently and makes multi-turn Codex conversations unusable.
Steps to reproduce
Expected behavior
"Hello 2" should be submitted and Codex should start the second turn.
Actual behavior
The first turn works normally.
After it completes, the second message can be typed into the composer, but it cannot be submitted.
The issue reproduces consistently in new conversations.
Troubleshooting already performed
%LOCALAPPDATA%\Codexand allowing the app to create a new one.None of these steps resolved the issue.
Relevant diagnostic logs
Around the failure, the diagnostic logs contain:
Received turn/started for unknown conversationfollowed by:
Received turn/completed for unknown conversationThe logs also showed a state where a thread was considered streaming without an active runtime.
This appears consistent with the UI/client losing synchronization with the conversation/turn state.
Feedback session ID
01a0da5b-c655-7101-b016-13bf39f9a3a9This Feedback report was submitted from the affected Codex Windows client with diagnostic logs enabled.
Environment
Additional information
OpenAI Support asked me to file this GitHub issue and include the Feedback session ID and the "unknown conversation" log entries.
I was also asked to test Codex web at chatgpt.com/codex, but while signed into the same account that URL only shows/redirects me to the ChatGPT desktop app download page, so I cannot currently compare the behavior with Codex web.