Windows app sends only the first message in every Codex chat
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What issue are you seeing?
In every new Codex chat in the Windows desktop app, I can send the first message successfully and receive a response. After that, the message composer becomes stuck and the second message cannot be sent.
If I create another new chat, I can again send exactly one message, after which the same issue occurs. I am also unable to continue existing chats.
The issue often occurs immediately after starting Windows and opening the app. If the app works correctly at startup, it usually continues working during that session.
Steps to reproduce
-
Open the ChatGPT/Codex Windows desktop app.
-
Open an existing project or create a new empty project.
-
Start a new Codex chat.
-
Send a simple first message.
-
Wait for Codex to respond.
-
Attempt to send a second message.
-
The second message remains stuck and is not submitted.
Expected behavior
Multiple messages should be sent normally within the same Codex chat.
Troubleshooting already completed
- ChatGPT web works normally with the same account.
- Reproduced in a completely new and empty project.
- Restarted the app and Windows multiple times.
- Ran Workspace Diagnose.
- Signed out and signed back in.
- Deleted and recreated the
.codexdirectory. - Completely uninstalled and reinstalled the Windows app multiple times.
- Tested different VPN servers.
- Tested v2rayN using TUN and Global mode.
- Confirmed that WinGet and Microsoft Store sources update successfully.
A clean reinstall previously resolved the issue temporarily, but it returned after several days. After the most recent clean reinstall, the problem occurred immediately.
Environment
ChatGPT/Codex app version: 26.909.22227
Operating system: Windows 10 Pro, version 22H2
OS build: 19045.6466
Architecture: x64
Previous OpenAI Support Case: 14284642
OpenAI Support directed me to file this GitHub issue and attach a minimal reproduction log.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the second-message failure in the Windows desktop app using the listed steps, then inspect the minimal reproduction log and the .codex state after the first response. The issue is done when new and existing Codex chats can submit multiple messages normally on the reported Windows environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100