Codex Desktop hangs after sending prompt on macOS

What version of the Codex App are you using?

Codex Desktop 26.601.21317 (CFBundleVersion 3511)

Bundled CLI:

codex-cli 0.136.0-alpha.2

What subscription do you have?

ChatGPT account. I can use Codex CLI successfully on the same machine/account.

What platform is your computer?

ProductName:    macOS
ProductVersion: 26.2
BuildVersion:   25C56
Darwin:         25.2.0 arm64

Apple Silicon Mac, arm64.

What issue are you seeing?

Codex Desktop opens and the shell UI loads, but starting a new chat and sending even a tiny prompt hangs forever.

Observed behavior:

• Sidebar loads.
• Projects load.
• Environment panel loads.
• New chat input is usable.
• After sending test, the app remains stuck loading and no assistant response appears.
• The CLI works, so this does not appear to be a general local Codex auth or CLI failure.
• Reinstalling the Codex app from the official macOS DMG did not fix it.
• Launching with a clean temporary app profile did not fix it.

Steps to reproduce

1. Open Codex Desktop on macOS.
2. Select any local project.
3. Click New chat.
4. Send:

test

1. Observe that the turn hangs indefinitely.

Expected behavior

Codex Desktop should start a turn and return a normal response for a trivial prompt like test.

Actual behavior

The UI stays in a loading state indefinitely. The user cannot get a response from Codex Desktop, even though the CLI works.

Troubleshooting already attempted

I tried the following without resolving the issue:

• Confirmed bundled CLI version:

/Applications/Codex.app/Contents/Resources/codex --version
codex-cli 0.136.0-alpha.2

• Checked app logs in:

~/Library/Logs/com.openai.codex/2026/06/03

• Killed stale old codex app-server and node_repl helper processes.
• Moved temporary bundled marketplace cache out of the way:

~/.codex/.tmp/bundled-marketplaces

• Removed deprecated config warning:

[features].web_search_request

• Pressed Settings > Reset and install Workspace. The UI said it could not reinstall dependencies, but logs reported the primary runtime as installed with problemCount=0.
• Temporarily disabled external MCP servers in ~/.codex/config.toml, including context7, stripe, and shaders. This did not fix the hang. Config was restored afterward.
• Reset Electron/browser cache folders under:

~/Library/Application Support/Codex

• Launched Codex with a clean temporary app profile:

~/Library/Application Support/Codex-clean-test-20260603-1253

The clean profile also hung.

• Reinstalled the Codex app from the official Apple Silicon DMG listed in the Codex docs:

https://persistent.oaistatic.com/codex-app-prod/Codex.dmg

The old app was moved aside and a fresh /Applications/Codex.app was installed. The issue still reproduces.

Relevant log snippets

Startup and CLI handshake succeed:

initialize_handshake_result durationMs=89 initializeRequestId=__codex_initialize__ outcome=success transportKind=stdio
Codex CLI initialized
app_server_connection.state_changed ... next=connected

Common repeated warnings/errors seen while the Desktop app hangs:

Statsig: error while bootstrapping post-login client ... path ["user", "custom", "workspace_type"] ... Invalid input
Timed out waiting for MCP response to marketplace/add
Timed out waiting for MCP response to experimentalFeature/list
Timed out waiting for MCP response to externalAgentConfig/detect

Dependency diagnosis says the primary runtime is installed:

primary_runtime_dependencies_diagnose_started hostId=local
primary_runtime_dependencies_diagnose_finished bundleVersion=26.601.10930 installed=true problemCount=0

After the hang, logs show normal app-server responses for many setup calls, but the user-visible turn never completes in the Desktop UI.

Similar existing reports

This looks related to these reports:

• #24287, Codex Desktop accepts prompt but UI stays stuck in Thinking
• #13715, macOS local Codex clients hang after sending prompts
• #24467, Codex Desktop threads remain spinning after long turns
• #11090, orphaned app-server processes and UI freezes

Additional notes

This does not look like a simple cache, profile, MCP, or app bundle corruption issue because the issue persists after:

• clean temporary profile
• external MCP disable test
• Electron cache reset
• fresh official app reinstall

The CLI is still usable on the same machine.