Critical WebSocket Conflict: Codex Windows App Stream Failure (Internal Socket Interference)

API Bugs
, , , ,
1

Technical Bug Report: Inter-Process Resource Conflict

Description: I am reporting a reproducible stream instability within the Codex Windows Application. The application frequently triggers a “Reconnecting” loop (1/5) followed by a terminal error.

Error Message: stream disconnected before completion: An error occurred while processing your request.

Root Cause Identification: After extensive isolation testing, I have identified a direct conflict with the ChatGPT Windows Desktop process.

  • Observation A: When the ChatGPT Desktop client is active in the background, the Codex stream (using GPT-5.4 X High) fails intermittently but frequently.

  • Observation B: Terminating all ChatGPT desktop processes immediately restores 100% stability to the Codex application.

This suggests a local resource lock or WebSocket port interference between the two native OpenAI Windows clients.

Environment & Model:

  • OS: Windows 10/11 (Native Desktop Apps)

  • Model: GPT-5.4 X High

  • Connection: WebSocket / Persistent Stream

Troubleshooting performed: I have already ruled out network-side issues (VPN, Firewall, and Proxy settings have been disabled/tested). The issue is strictly an inter-app conflict on the local OS.

Request: Could the engineering team investigate how these two applications manage simultaneous streaming connections on Windows to prevent this socket interference?

2 Likes
2

Update after further testing:

I have conducted several rounds of testing to isolate the cause, including clean system reboots. Here are my findings:

  • With ChatGPT Windows App open: There is approximately a 33% chance (1 in 3) of triggering the “Reconnecting” alert during a Codex task. While it sometimes recovers, it frequently hits the 5/5 failure limit and disconnects.

  • With ChatGPT Windows App closed: After multiple tests following a fresh reboot, I experienced zero reconnection alerts. The stream remains 100% stable.

Conclusion: While I cannot be 100% certain of the underlying technical reason, all empirical data points toward a direct conflict when running both applications simultaneously. It seems the Codex app and the ChatGPT desktop client do not coexist well on the same Windows environment, likely due to shared resource contention or socket interference.