macOS Codex Desktop completely unresponsive after latest update; restart and reboot do not recover
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What issue are you seeing?
Codex Desktop on macOS became completely unresponsive immediately after a recent app update. The app launches, but there is effectively no usable response from the UI.
This was working before the update, so this appears to be a regression introduced by the new Codex Desktop build. It may also involve compatibility with the current macOS release.
Steps already tried
- Quit and relaunch Codex Desktop
- Restart the Mac
- Launch Codex again after reboot
The problem persists after all of the above.
Steps to reproduce
- Use Codex Desktop normally on macOS.
- Update Codex Desktop to the latest available version.
- Launch the updated app.
- Observe that the app/UI is unresponsive.
- Quit/relaunch the app and reboot macOS.
- Observe that the app remains unresponsive.
Expected behavior
Codex Desktop should launch normally and the UI should remain responsive after updating.
Actual behavior
The updated Codex Desktop app is unusable because it does not respond, and restarting either the app or the computer does not resolve the issue.
Regression information
- The issue began only after updating Codex Desktop.
- The previous version was usable on the same Mac.
- Because the app is currently unresponsive, the exact Codex build number has not yet been captured from the About dialog.
- Exact macOS version/build can be added if needed.
Additional notes
There are other reports of Codex Desktop becoming unresponsive after updates, including macOS reports, but this report specifically describes a persistent post-update failure that survives both app restart and a full macOS reboot.
If maintainers need specific logs, process samples, the Codex build number, or the macOS build number, I can provide them in a follow-up.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is identified in the report. First collect the Codex build number, macOS version/build, and any requested logs or process samples, then reproduce the post-update hang; done means the updated app launches and its UI remains responsive after relaunch and reboot.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, rust
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100