›_ Codex Issues
Codex Issues / #8593

VS Code: Codex 5.2 constantly stuck on “Reconnecting” (worked fine before 5.2)

Resolved 💬 2 comments Opened Dec 29, 2025 by RelayZ Closed Dec 29, 2025
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

codex-cli 0.77.0

What subscription do you have?

Plus

Which model were you using?

5.2、codex-5.2

What platform is your computer?

MacOS 15.6、Ubuntu22

What issue are you seeing?

In VS Code, Codex 5.2 frequently gets stuck in a persistent “Reconnecting…” loop and never becomes available for use. There is no stable connection established, so features such as chat/code assistance cannot be used.

Observed behavior
• Status continuously flips to / stays at: Reconnecting…
• No successful connection state is reached (no “Connected/Ready”)
• The issue is continuous across restarts and persists for the entire session

Regression
• The same VS Code setup and network environment worked normally before Codex 5.2.
• The reconnect loop started only after upgrading to Codex 5.2.

What steps can reproduce the bug?

Steps

  1. Update to Codex 5.2 in VS Code.
  2. Open VS Code (fresh window).
  3. Open the Codex panel or invoke any Codex command.
  4. Observe Codex status enters Reconnecting… and does not recover.

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 8 months ago

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

  • #8583

Powered by Codex Action

etraut-openai contributor · 8 months ago

Thanks for reporting, but there's not enough information for us to diagnose the problem. A "reconnecting" message can occur for dozens of different reasons.

It's likely that you're seeing the issue that we're tracking in #8302.

If you experience this problem again, please look at the error message after the "Reconnecting 5/5" error — that is, the error that eventually causes the final failure after five retries.

If you're seeing a problem different from #8302, please use the /feedback slash command to upload your logs and session data and file a new bug with details.