Codex 0.142.5 Failed Websocket Initiation

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

0.142.5

What subscription do you have?

Pro

What platform is your computer?

MacOS 27.0 Beta 3

What issue are you seeing?

Environment
-----------
MacBook Pro M4 (Apple Silicon)
macOS 27 Beta 3
Codex Desktop 0.142.5
Codex CLI 0.142.5

Symptoms
--------

• Desktop app hangs indefinitely on startup.
• CLI works.
• Login succeeds.
• codex doctor hangs indefinitely at:

"Still checking websocket..."

Desktop log
-----------
Failed to initialize desktop settings:
failed to read configuration layers:
timed out waiting for cloud config bundle after 15s

Networking
----------

• Safari reaches ChatGPT normally.
• Atlas eventually loads.
• Google HTTPS works.
• curl https://api.openai.com consistently times out.
• Reproduced on both home Wi-Fi and work Wi-Fi.
• Packet capture shows successful TLS/QUIC traffic to multiple destinations, indicating general networking is healthy.

Troubleshooting performed
-------------------------

• Cleared Codex Application Support and caches.
• Reinstalled NordVPN.
• Verified DNS.
• Verified routing.
• Verified TLS to Google.
• Verified authentication (codex login status).
• Verified CLI version.
• Verified network extensions.
• Tested multiple networks.
• Captured network traffic with tcpdump/nettop.

Expected
--------
Desktop app should initialize normally.

Actual
------
Desktop app never progresses beyond initialization while waiting for cloud configuration/WebSocket initialization.

What steps can reproduce the bug?

Steps to Reproduce

1. Install/update Codex Desktop 0.142.5.
2. Run on macOS 27 Beta 3 (Apple Silicon).
3. Launch the Codex desktop application.
4. Wait for initialization.

Expected Behavior

The application should complete initialization and display the chat interface.

Actual Behavior

The application remains on the loading screen indefinitely.

Desktop logs consistently contain:

Failed to initialize desktop settings
failed to read configuration layers:
timed out waiting for cloud config bundle after 15s

Running:

codex doctor

never completes and remains at:

Still checking websocket...

codex login status reports:

Logged in using ChatGPT

Diagnostics Performed

To isolate the issue, I performed the following:

• Removed Codex Application Support and cache directories.
• Restarted multiple times.
• Verified Codex CLI installation.
• Verified authentication (codex login status).
• Confirmed codex-cli version is 0.142.5.
• Tested on both home Wi-Fi and work Wi-Fi with identical behavior.
• Confirmed Safari can successfully access ChatGPT and other OpenAI websites.
• Atlas eventually loads successfully.
• Verified DNS resolution.
• Verified general HTTPS connectivity.
• Verified TLS handshakes succeed to other destinations (e.g. Google).
• Inspected system extensions (Cisco Secure Client socket filter and Nord Threat Protection were present, although the issue persisted across troubleshooting).
• Captured network traffic using tcpdump/nettop.

Additional Observations

One interesting behavior is that:

• curl https://google.com succeeds normally.
• curl https://api.openai.com consistently times out establishing the TCP connection.
• Safari can still access ChatGPT successfully.
• Atlas eventually initializes.
• Codex Desktop never progresses beyond startup.
• codex doctor never progresses beyond websocket checking.

This started immediately after updating to macOS 27 Beta 3. Because both the OS and Codex were updated around the same time, I cannot conclusively determine whether this is a Codex regression, a macOS Beta compatibility issue, or an interaction between the two.

If additional debug logging or a development build would help isolate the websocket/configuration initialization failure, I'd be happy to test it.

---

P.S. If this turns out to be a genuine macOS Beta compatibility bug, I respectfully submit my application for honorary QA engineer status. Compensation in the form of a few complimentary months of ChatGPT Pro would be graciously accepted. 😄

What is the expected behavior?

_No response_

Additional information

_No response_