Macos 27 beta3 cannot submit task

Open 💬 6 comments Opened Jul 7, 2026 by TimmyYu

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

Version 26.623.141536 • Released Jul 7, 2026

What subscription do you have?

Gpt Pro

What platform is your computer?

Darwin 27.0.0 arm64 arm

What issue are you seeing?

After updating to macOS 27 Beta 3, the Codex App is no longer able to submit tasks. Every request eventually times out.

After investigating, it appears that the issue is related to stricter Unix socket restrictions introduced in the new macOS version. Could you please check whether the app needs to be updated to comply with the Unix socket requirements in macOS 27?

At the moment, only the Codex App is affected. The CLI version continues to work normally, which suggests the issue is specific to the app rather than the backend or the service itself.

What steps can reproduce the bug?

Feedback ID: 019f1dbd-6343-7692-a62e-1a1d799ebfb0

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

6 Comments

xriter · 12 days ago

Hitting the same thing. I just she 'Thinking', but a response never comes in.

I tried the CLI, and there I see these errors:

⚠ MCP client for `codex_apps` timed out after 30 seconds. Add or adjust `startup_timeout_sec` in your config.toml:
  [mcp_servers.codex_apps]
  startup_timeout_sec = XX

⚠ MCP startup incomplete (failed: codex_apps)

(not sure if it is related, but it might help?)

tiagobecker · 12 days ago

same here, Codex app don't open anymore since update to MacOS 27 beta 3.

tiagobecker · 12 days ago

🐛 Codex App fails to launch on macOS 27 Beta 3

💻 Environment

OS: macOS 27.0 (Build 26A5378j - Golden Gate Beta 3)
Codex Version: 0.142.5 (or similar desktop versions)

📝 Symptom

When attempting to launch the Codex Desktop App normally via the Finder or the Dock, the application fails to open and hangs or terminates immediately during initialization.

🔍 Root Cause

macOS 27 Beta 3 enforces stricter XPC service bootstrap and lookup restrictions. When launched through LaunchServices (the GUI wrapper), the OS blocks or fails to locate Codex's internal update/maintenance XPC helpers (e.g., com.openai.codex-spks), throwing the following errors in the macOS system log:

launchd[1]: [gui/501 [100031]:] failed lookup: name = com.openai.codex-spks, requestor = Codex[PID], error = 3: No such process
Codex[PID]: (libxpc.dylib) [com.apple.xpc:connection] failed to do a bootstrap look-up: xpc_error=[3: No such process]
Codex[PID]: (libxpc.dylib) [com.apple.xpc:connection] invalidated after a failed init

This bootstrap failure invalidates the main process's IPC connection, causing it to crash or exit silently.

🛠️ Workarounds

1. Launch Directly via Terminal

Running the application binary directly from the terminal bypasses the restrictive launchd GUI session bootstrap lookup path:
/Applications/Codex.app/Contents/MacOS/Codex

_Note: You can also use open /Applications/Codex.app in the terminal to spawn it._

2. Kill Orphaned Background Processes

If the app still fails to initialize after using the terminal, it might be due to orphaned app-server or node processes left behind from previous sessions. Kill them before relaunching:
killall -9 Codex "Codex (Service)" "Codex (Renderer)" codex

knifeknifeknifeknife · 12 days ago

same problem on macos27 beta3, messages sent in the codex app goes into "Thinking" forever.

TimmyYu · 10 days ago

After updating to Beta 3, the original AnyConnect SPI no longer works because it is incompatible with the current Apple system.
To resolve this issue, go to System Settings and disable the old SPI configuration. After disabling the previous SPI settings, AnyConnect can be used normally again.

TimmyYu · 10 days ago

The issue I was experiencing has been resolved.