Codex Went Silent For 46 Minutes. Then It Blamed The Wait On Itself.
A bug report filed October 1 describes repeated websocket timeouts in the Codex Windows app and an answer that glossed over them. On Reddit, other users say the disconnects have run for two days.
A server rack full of network cables, shown for illustration. Photo: Kim Scarborough, CC BY-SA 2.0, via Wikimedia Commons.
If you've used Codex this week and watched it say "reconnecting" over and over, you're not alone. On Thursday, October 1, a user filed issue 50086 on OpenAI's own Codex repository on GitHub, and it reads like a lot of the complaints we've been collecting.
What the bug report says
The reporter was running a long task in the Codex desktop app on Windows, package version 26.928.3736.0 with Codex CLI 0.159.2. The response stream kept dropping with the same message: "stream disconnected before completion: idle timeout waiting for websocket." Screenshots in the issue show the app counting through reconnection attempts.
The agent's own tool log shows a gap of about 46 minutes, from 19:18 to 20:04 UTC. That's 12:18 to 1:04 PM Pacific. For roughly 40 minutes, the user got no answer at all.
The part that stings
When the stream finally recovered, the assistant didn't say the connection had failed. According to the report, it opened with "I'm here. I should have kept you updated more promptly" and went straight into a project update. The reporter says it only acknowledged the disconnects after being shown the evidence.
That's the real complaint here. Outages happen. An assistant that explains a transport failure as its own slow reporting leaves you unsure what actually ran during the gap. The reporter asks OpenAI to look at how Codex recovers from these timeouts and whether the model is even told that the transport failed. No maintainer reply was visible when we read the issue.
It isn't one machine
The same day on r/codex, a user posted that Codex had been "basically unusable for two days," with constant "error decoding response body" and "idle timeout waiting for websocket" errors. They said it edits a few files, then gets stuck reconnecting forever, on an updated Windows app, after restarts, across models and new chats, with no VPN.
Another r/codex user on the 20x Pro plan said that while working with Sol 6.1 their remaining weekly limit went from around 35 percent to zero "just like a snap of the fingers," and that 10k granted credits were gone within minutes.
Where the status page stands
OpenAI's status history shows incidents on September 29 and September 30, including elevated errors for ChatGPT Pro and Plus users and elevated latency for some API requests. When we checked it on the afternoon of October 1, it listed no incident for that day, even as these reports were coming in.
If Codex drops on you mid task, check the actual diff and tool log before trusting the summary it gives you afterward. That's what this user had to do.
Sources: openai/codex issue 50086; r/codex, October 1; r/codex, October 1; OpenAI status history.