You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
"Cloud" conversations no longer connected and removed from Codex #51118
What version of the Codex App are you using (From “About Codex” dialog)?
26.930.41038
What subscription do you have?
Pro x5
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
As per the title, as of about 15 minutes ago, I lost connectivity to my Cloud conversations I had started, getting a 403 error. Then I restarted Codex and now they have all just disappeared.
What steps can reproduce the bug?
Open up Codex after having some Cloud conversations and see they are no longer there.
What is the expected behavior?
They should still be there and be able to use them as expected.
Also seeing this Version 26.930.51102 on MacOS 15.2. No cloud tasks visible in Codex but available via web app. Unlike @Chris-Duke, I can message them via web.
Observed October 5, 2026; times below are UTC (PDT + 7 hours):
15:41:13: the durable WebSocket closed with code 1006, followed by repeated "Unexpected server response: 403" failures. The local app-server connection remained healthy.
Around 16:49: restarting the app did not restore the durable connection.
16:55:03: clicking Reconnect returned 403 after approximately 137 ms.
During the failure, native MCP calls also returned -32000 / "Transport closed."
17:39:49: the durable connection initialized successfully without another repair action. Native reads of two existing tasks then succeeded.
I'm not using a VPN, proxy or corporate network. My network uses a Ubiquiti router with IPv6 and secure DNS. I haven't established a network cause, captured the authenticated handshake response headers/body, or confirmed a connection to today's reported Work incident.
The connection recovered, but cloud-chat history remained partially visible or blank. I'm adding that separately to #50796 so connection recovery isn't mistaken for full UI recovery.
I submitted in-app feedback at approximately 18:15 UTC. Feedback ID: 01a0fe60-be10-7734-a40b-5325f1064033.
Please use that feedback to correlate the failed durable handshakes with the later successful initialization. Private conversation contents, task identifiers and raw logs are omitted.
Same goes for me. The session no longer appears in the desktop app (windows), in the web, and in the mobile App too. Looked in the archived chats too, and it doesn't even appear there.
Activity
github-actions commentedon Oct 5, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Chris-Duke commentedon Oct 5, 2026
The cloud conversations appear to be in place in Codex/ChatGPT website but you cannot message in them.
adamsvoboda commentedon Oct 5, 2026
broken for me as well as of about 30 minutes ago, all cloud convos are unusable, cant open them at all
same 403 error, latest app 26.930.51102 / build 13100 on macos27
rianquinn commentedon Oct 5, 2026
Same issue. All cloud tasks a gone.
Benjamin-Lee commentedon Oct 5, 2026
Also seeing this Version 26.930.51102 on MacOS 15.2. No cloud tasks visible in Codex but available via web app. Unlike @Chris-Duke, I can message them via web.
mxssmu commentedon Oct 5, 2026
I'm seeing the same cloud-connection failure on macOS, including the exact app build reported above.
Environment: ChatGPT/Codex desktop 26.930.51102 (build 13100), macOS 27.0.1 (26A434), bundled Codex CLI 0.160.0.
Observed October 5, 2026; times below are UTC (PDT + 7 hours):
I'm not using a VPN, proxy or corporate network. My network uses a Ubiquiti router with IPv6 and secure DNS. I haven't established a network cause, captured the authenticated handshake response headers/body, or confirmed a connection to today's reported Work incident.
The connection recovered, but cloud-chat history remained partially visible or blank. I'm adding that separately to #50796 so connection recovery isn't mistaken for full UI recovery.
I submitted in-app feedback at approximately 18:15 UTC. Feedback ID: 01a0fe60-be10-7734-a40b-5325f1064033.
Please use that feedback to correlate the failed durable handshakes with the later successful initialization. Private conversation contents, task identifiers and raw logs are omitted.
lukemxlr commentedon Oct 6, 2026
Same goes for me. The session no longer appears in the desktop app (windows), in the web, and in the mobile App too. Looked in the archived chats too, and it doesn't even appear there.