›_ Codex Issues
Codex Issues / #28485

Codex Computer Use helper reported damaged after latest desktop app update

Open 💬 2 comments Opened Jun 16, 2026 by GGBondBlueWhale
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Summary

After updating Codex Desktop to the latest version and letting the app auto-restart, macOS reports that the Codex Computer Use helper is damaged and cannot be opened.

The dialog says:

“Codex Computer Use” is damaged and can’t be opened. You should move it to the Trash.

This still occurs on the latest build I just updated to, so the issue does not appear to be fixed yet.

Environment

  • Codex Desktop version: 26.609.71450
  • About window release date: Jun 15, 2026
  • macOS: Tahoe 26.5.1
  • Device: MacBook Pro 16-inch, Apple M5 Max, 128 GB memory

Steps to reproduce

  1. Update Codex Desktop to version 26.609.71450.
  2. Let Codex complete the update and restart automatically.
  3. Observe the macOS warning for Codex Computer Use.

Expected behavior

The Codex app and its helper components should launch normally after an update/restart.

Actual behavior

macOS blocks Codex Computer Use and reports that it is damaged and cannot be opened.

Impact

This seriously affects use of Codex Desktop because the helper appears unusable after update/restart, and it can make the app unstable during normal use.

Please investigate the signing/notarization/quarantine handling for the Codex Computer Use helper in the latest desktop app build.

<img width="520" height="560" alt="Image" src="https://github.com/user-attachments/assets/a4931d02-ccce-4af1-8a6f-658d7a4d4d08" />

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 2 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #28184
  • #28274
  • #28404

Powered by Codex Action

omarpinarecords · 2 months ago

Cross-linking a related in-app report: Feedback ID 019ed2cb-eea6-7851-be4d-8be66a992d92.

I also added the fuller diagnostic note here: https://github.com/openai/codex/issues/27662#issuecomment-4724737107

In my case the visible dialog named openai rather than Codex Computer Use, but the local diagnostics point to the same macOS Gatekeeper/SystemPolicy failure family: spctl failed even for /bin/ls with internal error in Code Signing subsystem, and also failed for Codex, Cursor, a normal Markdown file, and /opt/homebrew/bin/openai.