›_ Codex Issues
Codex Issues / #29794

After updating to the new version today, Codex Desktop for Mac keeps showing 'reconnecting'.

Open 💬 2 comments Opened Jun 24, 2026 by Fitz-liu
💡 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)?

Codex 26.616.81150

What subscription do you have?

Pro

What platform is your computer?

Mac M1 pro

What issue are you seeing?

stream disconnected before completion: error sending request for url (https://chatgpt.com/backend-api/codex/responses)

What steps can reproduce the bug?

stream disconnected before completion: error sending request for url (https://chatgpt.com/backend-api/codex/responses)

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 2 months ago

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

  • #29609

Powered by Codex Action

Fitz-liu · 2 months ago

Title:
Codex Desktop conversation stuck reconnecting after turn/start succeeded

Description:
A newly created Codex Desktop conversation became stuck in a reconnecting state. The conversation was created successfully and turn/start returned success, but the assistant never produced any output or tool calls. The turn was later aborted after about 100 seconds.

Observed behavior:

  • A new conversation was created successfully.
  • turn/start returned successfully.
  • The UI kept showing reconnecting / stuck state.
  • The assistant never emitted output or tool calls.
  • The session only contained metadata, the user message, and then turn_aborted.
  • The turn had to be manually interrupted.

Relevant log evidence:

  • Conversation created successfully.
  • turn/start response was routed successfully with no error.
  • Shortly before and after that, multiple Codex API requests failed with:
  • net::ERR_CONNECTION_CLOSED

Affected endpoints included:

  • /wham/accounts/check
  • /wham/environments
  • /wham/tasks/list
  • /beacons/home

There was also a remote-control state issue:

  • remote-control state became disconnected
  • The app logged: Received turn/started for unknown conversation

Expected behavior:
If Codex Desktop temporarily loses API / remote-control connectivity, it should either recover the active turn cleanly or mark the turn as failed with a clear error.

Actual behavior:
The conversation stayed stuck/reconnecting after turn/start had already succeeded. No assistant response or tool calls were produced, and the user had to manually interrupt the turn.

Impact:
This makes the affected conversation unusable and can make it look like the model is still working or reconnecting, when the turn is actually stuck.