tccutil reset All com.openai.codex

Open 💬 1 comment Opened Apr 24, 2026 by AndrewDavidBaron

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

Codex Desktop App v26.422.21637 Codex CLI: v0.124.0 (bundled app-server reports 0.124.0-alpha.2)

What subscription do you have?

ChatGPT Plus

What platform is your computer?

MacBook Pro (16-inch, 2021) Apple M1 Pro 16 GB RAM macOS Tahoe 26.2

What issue are you seeing?

The Codex Desktop App launches but remains stuck in a non-interactive, blank/hung UI state.

Key observations:

App launches successfully
UI renders but remains idle / unresponsive
No ability to start a conversation or interact
Appears “hung” indefinitely

However, backend logs show:

Successful app-server spawn
Successful stdio transport initialization
Successful handshake
Connection state transitions to connected

Example logs:

initialize_handshake_result outcome=success
Codex CLI initialized
state_changed ... next=connected

This indicates:

👉 Backend is functioning correctly
👉 Issue appears isolated to the UI / Electron layer

🧪 Steps to reproduce
Install Codex Desktop App (latest version)
Launch application
Observe UI remains blank / non-interactive indefinitely
🧪 Troubleshooting attempted
Full uninstall + reinstall of Codex app
Cleared all local state:
~/Library/Application Support/Codex
~/Library/Caches/Codex
~/Library/Preferences/com.openai.codex.plist
Restarted system

Reset macOS permissions:

tccutil reset All com.openai.codex

Verified CLI functionality:

codex

→ CLI works normally

Launched app via binary:

/Applications/Codex.app/Contents/MacOS/Codex

→ backend initializes successfully

🧠 Additional context
Issue persists across fresh installs
Occurs on macOS Tahoe 26.2 (Apple Silicon)
CLI functionality is unaffected
Appears consistent with UI-level deadlock or rendering failure

🧭 Summary

Codex Desktop App successfully initializes backend services but fails to transition into a usable UI state. The issue appears isolated to the frontend layer and is reproducible across clean installs.

What steps can reproduce the bug?

...

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗