codex unusable due to continuous reconnection loop and stream disconnections
What version of the Codex App are you using (From “About Codex” dialog)?
Codex 26.519.81530
What subscription do you have?
ChatGPT Pro
What platform is your computer?
Microsoft Windows 10 Pro Windows Version: 2009 OS Build: 10.0.26100.1 64-bit
What issue are you seeing?
Asunto: Codex unusable due to continuous reconnection loop and stream disconnections
Hello OpenAI Support,
I am experiencing a persistent issue with Codex that started on May 28, 2026 and is still occurring on May 29, 2026.
Environment:
- ChatGPT Pro
- Codex accessed through chatgpt.com
- Windows 11
- Google Chrome (also reproduced in other browser sessions)
Problem:
Every Codex task enters a reconnection loop and never completes. The interface repeatedly shows:
Reconnecting... 1/5
Reconnecting... 2/5
Reconnecting... 3/5
Reconnecting... 4/5
Reconnecting... 5/5
After several attempts, the following error appears:
"stream disconnected before completion: error sending request for url (https://chatgpt.com/backend-api/codex/responses)"
Impact:
- Codex is effectively unusable.
- Tasks fail before completion.
- The problem has persisted for more than 24 hours.
- Multiple retries produce the same result.
Troubleshooting already attempted:
- Refreshing the page
- Logging out and back in
- Using different browser sessions
- Verifying internet connectivity
- Retrying multiple times over two consecutive days
Please confirm whether this is a known service issue affecting Codex and whether there is an estimated time for resolution.
I have attached a screenshot showing the error.
Thank you.
What steps can reproduce the bug?
- Launch Codex Desktop App version 26.519.81530.
- Sign in with a ChatGPT Pro account.
- Create a new conversation.
- Enter any prompt, including very simple prompts such as:
- hello
- create a file named test.txt
- explain recursion
- Submit the prompt and wait for the response.
- Codex begins generating a response but repeatedly enters:
Reconnecting... 1/5
Reconnecting... 2/5
Reconnecting... 3/5
Reconnecting... 4/5
Reconnecting... 5/5
- After several reconnection attempts, the request fails with:
stream disconnected before completion: error sending request for url (https://chatgpt.com/backend-api/codex/responses)
Expected result:
Codex completes the response normally.
Actual result:
The response stream disconnects repeatedly and the task never completes.
Frequency:
100% reproducible since May 28, 2026.
Additional notes:
- Occurs with both existing and newly created conversations.
- Occurs with simple and complex prompts.
- Internet connection is stable.
- The issue has persisted for more than 24 hours.
- Screenshots attached.
What is the expected behavior?
_No response_
Additional information
The issue appears specifically related to the Codex backend endpoint:
/backend-api/codex/responses
The behavior suggests that the response stream is being interrupted before completion, causing repeated reconnection attempts followed by failure.
6 Comments
These types of connectivity problems are often caused by network instability or local VPN/proxy issues.
You could try installing the Codex CLI and running
codex doctor. This will run some diagnostics and give you a report.Thanks for the suggestion.
I ran codex doctor on the affected machine.
Key findings:
-
No proxy configured.
-
OpenAI endpoints are reachable.
-
DNS resolution works.
-
HTTPS connectivity works.
-
Codex CLI 0.135.0 authenticates and works correctly.
-
Browser authentication works correctly.
-
localhost OAuth callback is functioning.
The only warning reported was:
"Responses WebSocket failed"
with:
"401 Unauthorized: Missing bearer or basic authentication in header"
which appears to indicate the endpoint is reachable and responding, rather
than a network connectivity failure.
Codex Desktop 26.519.11010.0 still fails with:
token_exchange_failed
Token exchange failed:
error sending request for url (https://auth.openai.com/oauth/token)
while Codex CLI works correctly on the same machine, account, network, and
operating system.
This appears isolated to Codex Desktop authentication rather than general
connectivity.
this is the Report:
PS C:\Users\Dr Gio> codex doctor
Codex Doctor v0.135.0 · windows-x86_64
Notes
⚠ rollouts 274 active files · 3.30 GB on disk
⚠ sandbox filesystem unrestricted · network enabled
⚠ websocket Responses WebSocket failed; HTTPS fallback may still work
⚠ threads rollout files are missing from the state DB
─────────────────────────────────────────────────────────────
Environment
✓ system es-MX
os Windows 10.0.26200 (Windows 11 Professional)
[64-bit]
OS language es-MX
✓ runtime npm (package C:\Users\Dr
@.****@.\codex-win32-x64\vendor\x86_64-pc-windows-msvc,
bin C:\Users\Dr
@.**@.\codex-win32-x64\vendor\x86_64-pc-windows-msvc\bin,
resources C:\Users\Dr
@.**@.\codex-win32-x64\vendor\x86_64-pc-windows-msvc\codex-resources,
path C:\Users\Dr
@.**@.\codex-win32-x64\vendor\x86_64-pc-windows-msvc\codex-path)
version 0.135.0
install method npm (package C:\Users\Dr
@.**@.\codex-win32-x64\vendor\x86_64-pc-windows-msvc,
bin C:\Users\Dr
@.**@.\codex-win32-x64\vendor\x86_64-pc-windows-msvc\bin,
resources C:\Users\Dr
@.**@.\codex-win32-x64\vendor\x86_64-pc-windows-msvc\codex-resources,
path C:\Users\Dr
@.**@.\codex-win32-x64\vendor\x86_64-pc-windows-msvc\codex-path)
commit unknown
executable C:\Users\Dr
@.**@.\codex-win32-x64\vendor\x86_64-pc-windows-msvc\bin\codex.exe
✓ install consistent
context npm (package C:\Users\Dr
@.**@.\codex-win32-x64\vendor\x86_64-pc-windows-msvc,
bin C:\Users\Dr
@.**@.\codex-win32-x64\vendor\x86_64-pc-windows-msvc\bin,
resources C:\Users\Dr
@.**@.\codex-win32-x64\vendor\x86_64-pc-windows-msvc\codex-resources,
path C:\Users\Dr
@.**@.\codex-win32-x64\vendor\x86_64-pc-windows-msvc\codex-path)
managed by npm: yes · bun: no · package root
C:\Users\Dr @.*\codex
PATH entries (2) C:\Users\Dr Gio\AppData\Roaming\npm\codex
C:\Users\Dr Gio\AppData\Roaming\npm\codex.cmd
npm update target C:\Users\Dr
@.*\codex
✓ search file exists (bundled, C:\Users\Dr
@.**@.\codex-win32-x64\vendor\x86_64-pc-windows-msvc\codex-path\rg.exe)
search command C:\Users\Dr
@.**@.**\codex-win32-x64\vendor\x86_64-pc-windows-msvc\codex-path\rg.exe
search provider bundled
search command readiness file exists
✓ git git version 2.49.0.windows.1
selected git C:\Program Files\Git\cmd\git.exe
version git version 2.49.0.windows.1
exec path C:/Program Files/Git/mingw64/libexec/git-core
repo detected false
PATH entries (1) C:\Program Files\Git\cmd\git.exe
✓ terminal unknown
terminal unknown
stdin is terminal true
stdout is terminal true
stderr is terminal true
terminal size 187x70
color output enabled
console input code page 437
console output code page 437
stdout console mode 0x00000007 (VT processing: true)
stderr console mode 0x00000007 (VT processing: true)
✓ title default · project Dr Gio
title source default
title items activity, project-name
activity item true
project source cwd
project value Dr Gio
✓ state databases healthy
CODEX_HOME C:\Users\Dr Gio\.codex (dir)
log dir C:\Users\Dr Gio\.codex\log (dir)
sqlite home C:\Users\Dr Gio\.codex (dir)
state DB C:\Users\Dr Gio\.codex\state_5.sqlite (file)
· integrity ok
log DB C:\Users\Dr Gio\.codex\logs_2.sqlite (file)
· integrity ok
goals DB C:\Users\Dr Gio\.codex\goals_1.sqlite (file)
· integrity ok
memories DB C:\Users\Dr Gio\.codex\memories_1.sqlite
(file) · integrity ok
active rollouts 274 files · 3.30 GB (avg 12.34 MB)
archived rollouts 26 files · 8.71 MB (avg 343.05 KB)
⚠ threads rollout files are missing from the state DB
default model provider openai
rollout DB active files 274
rollout DB archived files 26
rollout DB scan errors 0
rollout DB malformed file names 0
rollout DB scan cap reached false
rollout DB rows 297
rollout DB active rows 274
rollout DB archived rows 23
rollout DB missing active rows 0
rollout DB missing archived rows 3
rollout DB stale rows 0
rollout DB archive mismatches 0
rollout DB duplicate rollout thread ids 0
rollout DB duplicate DB paths 0
rollout DB model providers openai=297
rollout DB sources vscode=239, subagent:thread_spawn=20,
cli=18, subagent:memory_consolidation=18, subagent:other=2
rollout DB missing archived sample C:\Users\Dr
Gio\.codex\archived_sessions\rollout-2026-05-17T21-11-38-019e38da-682a-7012-80c6-f21652d18dcf.jsonl
rollout DB missing archived sample C:\Users\Dr
Gio\.codex\archived_sessions\rollout-2026-05-17T21-11-38-019e38da-6833-7ad0-a31b-1776fdcdcdf3.jsonl
rollout DB missing archived sample C:\Users\Dr
Gio\.codex\archived_sessions\rollout-2026-05-20T08-36-00-019e4599-b0cd-7203-8284-cc2fdd1a7660.jsonl
Configuration
✓ config loaded
model gpt-5.5 · openai
cwd C:\Users\Dr Gio
config.toml C:\Users\Dr Gio\.codex\config.toml
config.toml parse ok
MCP servers 0
feature flags 27 enabled · 1 overridden (full list with
--all)
overrides memories
✓ auth auth is provided by environment
auth storage mode File
auth file C:\Users\Dr Gio\.codex\auth.json
auth env vars present OPENAI_API_KEY
✓ mcp no MCP servers configured
✓ sandbox unrestricted fs + enabled network · approval OnRequest
approval policy OnRequest
filesystem sandbox unrestricted
network sandbox enabled
linux helper none
execve wrapper helper none
Updates
✓ updates update configuration is locally consistent
startup update check true
update action npm install -g @openai/codex
version cache C:\Users\Dr Gio\.codex\version.json
cached latest version 0.135.0
last checked at 2026-05-29 16:51 UTC
npm update target C:\Users\Dr
@.***\codex
latest version 0.135.0
latest version status current version is not older
Connectivity
✓ network no proxy env vars
proxy env vars none
⚠ websocket Responses WebSocket failed; HTTPS fallback may still work
— Check proxy, VPN, firewall, DNS, custom CA, and WebSocket policy support.
model provider openai
provider name OpenAI
wire API responses
supports websockets true
proxy env vars none
connect timeout 15000 ms
auth mode none
endpoint wss://api.openai.com/v1/<redacted>
DNS 2 IPv4, 0 IPv6, first IPv4
handshake transport error http 401 Unauthorized: Some("{\n
\"error\": {\n \"message\": \"Missing bearer or basic authentication in
header\",\n \"type\": \"invalid_request_error\",\n \"param\": null,\n
\"code\": null\n }\n}")
✓ reachability active provider endpoints are reachable over HTTP
reachability mode API key auth
openai API base URL https://api.openai.com/v1 reachable (HTTP
404)
openai API route probe https://api.openai.com/v1/<redacted> route
exists (HTTP 401)
Background Server
○ app-server not running (ephemeral mode)
daemon state dir C:\Users\Dr Gio\.codex\app-server-daemon
settings C:\Users\Dr
Gio\.codex\app-server-daemon\settings.json (missing)
pid file C:\Users\Dr
Gio\.codex\app-server-daemon\app-server.pid (missing)
update-loop pid file C:\Users\Dr
Gio\.codex\app-server-daemon\app-server-updater.pid (missing)
control socket C:\Users\Dr
Gio\.codex\app-server-control\app-server-control.sock
status not running
mode ephemeral
─────────────────────────────────────────────────────────────
15 ok · 1 idle · 4 notes · 2 warn · 0 fail degraded
--summary compact output --all expand truncated lists
--json redacted report
PS C:\Users\Dr Gio>
El vie, 29 may 2026 a las 13:16, Eric Traut @.***>)
escribió:
Hi Eric,
Thank you for the suggestion. As I mentioned, I ran
codex doctor
and the report confirms that the problem appears to be isolated to Codex
Desktop authentication, as the CLI works correctly on the same machine,
account, and network.
1 <https://mail.google.com/mail/u/0/#all/19e7505283eddd6c>
To help rule out a possible regression in the current desktop app version,
I wanted to ask: *Is there a way to install a previous Codex Desktop build
for testing?*
Best regards,
Giovanny Ponte
El vie, 29 may 2026 a las 13:35, Giovanny Ponte @.***>)
escribió:
Hi Eric,
Thank you
The issue appears to have been resolved after updating Codex Desktop from
version 26.519.11010.0 to 26.527.3378.0.
After the update, authentication completed successfully and Codex Desktop
is now working normally.
Based on the troubleshooting results and the fact that the issue
disappeared immediately after updating, it appears the problem may have
been related to the previous Desktop build rather than a local network
configuration issue.
Thank you for your help and for pointing me to codex doctor.
El vie, 29 may 2026 a las 14:39, Giovanny Ponte @.***>)
escribió:
done thank you
El vie, 29 may 2026 a las 16:05, Eric Traut @.***>)
escribió:
Same issue, the thread ID is 019f826c-46ee-7d82-af77-7b3178dcefed.