Codex app stuck on loading screen / unable to authenticate on macOS 27 Beta 3

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

26.623.141536

What subscription do you have?

Plus

What platform is your computer?

Darwin 27.0.0 arm64 arm

What issue are you seeing?

Description

After updating to macOS 27 Beta 3 (Build 26A5378j), the Codex desktop app fails to launch normally via the GUI. When launched via terminal to bypass the GUI block, the app opens but is unable to complete the authentication flow, getting permanently stuck on "Continue your login in the browser".

Root Cause Analysis

This is caused by Apple's new, stricter networking and XPC sandbox restrictions introduced in macOS 27 Beta 3 affecting the bundled Electron/Node environment:

1. XPC Block (Launch Failure): When launched via the macOS GUI (launchd), the OS blocks the com.openai.codex-spks (Sparkle Updater) XPC bootstrap, causing the app to hang indefinitely on the initial loading screen.
2. Network Sandbox Block (Auth Failure): When bypassing the GUI by launching the binary directly from the terminal (/Applications/Codex.app/Contents/MacOS/Codex), the internal Chromium network stack is blocked from making outbound connections.

• The local OAuth callback server (localhost:1455) accepts TCP connections but drops HTTP requests.
• Internal requests to chatgpt.com endpoints and Statsig telemetry fail with net::ERR_TIMED_OUT (e.g., [Statsig] A networking error occurred... Error: Timeout of 10000ms expired).

As a result, even if the OAuth callback is manually injected via deep link (codex://auth/callback...), the Electron renderer cannot exchange the code for an access token due to the blocked outbound HTTPS requests.

What steps can reproduce the bug?

Steps to Reproduce

1. Update a Mac to macOS 27 Beta 3 (Build 26A5378j).
2. Attempt to open Codex via the Dock or Applications folder (gets stuck on loading screen).
3. Force-close processes and launch via terminal: /Applications/Codex.app/Contents/MacOS/Codex
4. Attempt to log in. The browser will say "Login successful", but the Codex app will remain stuck on the login screen because it cannot fetch the token.

Environment

• OS: macOS 27 Beta 3 (Build 26A5378j)
• App Version: Codex v0.142.5 (Prod)
• Architecture: ARM64 / x86_64

What is the expected behavior?

_No response_

Additional information

_No response_