Reconnecting Issues

Open 💬 9 comments Opened May 25, 2026 by HaydenSDK
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

26.519.41501

What subscription do you have?

Pro

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

stream disconnected before completion: Transport error: network error: error decoding response body

What steps can reproduce the bug?

Consistantly getting reconnecting errors, with nearly every prompt to Codex. Any prompt will cause this error, different sessions/chats ect, at somepoiunt they will start just reconnecting for ages at a time. Network is 1Gbps down/up and stable, not had issues with other 3rd-party systems.

Feedback ID: 019e302f-24b9-7173-9c3d-fd547fe3bc9b

<img width="283" height="217" alt="Image" src="https://github.com/user-attachments/assets/fc5454d8-ed47-4962-aa1e-64dddd356d33" />

<img width="429" height="698" alt="Image" src="https://github.com/user-attachments/assets/a450843f-f7fa-4d9c-85d9-39d2cf59161c" />

What is the expected behavior?

Not to disconnect with every prompt.

Additional information

_No response_

View original on GitHub ↗

9 Comments

github-actions[bot] contributor · 1 month ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #23061
  • #23842
  • #24045

Powered by Codex Action

HaydenSDK · 1 month ago

<img width="187" height="757" alt="Image" src="https://github.com/user-attachments/assets/74fc4334-c5c6-4d6a-903b-d92cb1abe1f1" />

David-Ai-Youtube · 1 month ago

I have been having same issue last 2 days.

GGBondBlueWhale · 1 month ago

I’m seeing similar reconnecting and stability issues over the past two days as well. Codex has also felt noticeably slower than usual on my side, including for relatively simple tasks.

This does not seem related to my local machine or network. It feels like a recent service-side regression affecting speed and reliability. It would be helpful if the team could investigate whether anything changed recently.

MichaelDevine · 1 month ago

Same issue here. I'm using the openai.chatgpt extension in VS Code in a Dev Container running Ubuntu 24.04. Host is Windows 11.

I experience this issue when I log in using an api key. Logging in via the browser also results in connectivity issues, example from the web login side shown.

<img width="764" height="358" alt="Image" src="https://github.com/user-attachments/assets/debbfb71-3c70-4157-adfc-52adff4bf2a4" />

This is what the openai.chatgpt VS Code extension logs in the Terminal window for this failure:

2026-05-26 19:42:22.057 [error] [CodexMcpConnection] cli: message="2026-05-26T19:42:22.056568Z ERROR codex_login::server: oauth token exchange transport failure is_timeout=false is_connect=true is_request=true error=error sending request for url (https://auth.openai.com/oauth/token)\nToken exchange error: error sending request for url (https://auth.openai.com/oauth/token)"
2026-05-26 19:42:22.057 [error] [CodexMcpConnection] cli: message="codex_login::server: login callback token exchange failed"
2026-05-26 19:42:22.074 [info] remote_chatgpt_login_port_forward_stop_skipped hostId=local loginId=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX trigger=completed

guido52six · 1 month ago

Codex app for Windows here. Same thing:

stream disconnected before completion: Transport error: network error: error decoding response body

My feedback ID: 019e45e9-45b7-7ed3-8246-95d77e393a43

HaydenSDK · 1 month ago

Still happening daily.
<img width="245" height="312" alt="Image" src="https://github.com/user-attachments/assets/d12c46c6-65b4-4210-b086-d7c869f9f5b7" />

MichaelDevine · 1 month ago

I was able to resolve this by adding ca-certificates to my apt install list in my Dockerfile and adding the following command:

RUN update-ca-certificates

LukasWillin · 1 month ago

It's pretty annoying and often (on the daily) makes codex barely usable, having to constantly type "continue" and the likes into the chat.

There are a few things that I can now say with pretty high certainty:

  • The issue becomes worse around 14:00 ~ 15:00 CEST (UTC+2), which is around 08:00 EDT (UTC-4) when the american continent starts it's work shifts (same was noted by my work colleagues independently).
  • It happens often when codex has to wait for long running tasks like test output etc.
  • At least this one should definitely not happen. Codex should resume without interruption once any cli command is finished.