›_ Codex Issues
Codex Issues / #28600

Codex Computer Use still reported damaged after 26.611.61049 update and auto-restart

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

Summary

After updating Codex Desktop to the newest build and letting the app restart automatically, macOS still reports that the Codex Computer Use helper is damaged and cannot be opened.

This means the issue is still not fixed in the latest version I just installed.

Environment

  • Codex Desktop version: 26.611.61049
  • About window release date: Jun 16, 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.611.61049.
  2. Let Codex complete the update and restart automatically.
  3. After restart, macOS shows a warning for Codex Computer Use.

Expected behavior

After the update and automatic restart, Codex Desktop and its helper components should open normally.

Actual behavior

macOS reports that Codex Computer Use is damaged and cannot be opened, and prompts the user to move it to the Trash.

Impact

This continues to seriously affect usage of Codex Desktop. The Computer Use helper remains unusable after updating, and this can make the Codex app unstable or cause crashes during normal use.

Please prioritize fixing the packaging/signing/notarization/quarantine handling for the Codex Computer Use helper in the latest Codex Desktop build.

<img width="520" height="560" alt="Image" src="https://github.com/user-attachments/assets/927a4d63-b9a9-41cd-8b63-170be36b2641" />

View original on GitHub ↗

6 Comments

github-actions[bot] contributor · 1 month ago

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

  • #28485
  • #28274
  • #28184

Powered by Codex Action

rhdtl78 · 1 month ago

Update: still reproduces after 26.611.61753 (4008)

This still reproduces after updating Codex Desktop again.

Environment

  • Codex Desktop: 26.611.61753 / build 4008
  • Bundle identifier: com.openai.codex
  • Codex Computer Use helper copied under ~/.codex/computer-use: version 1.0, build 810
  • Date observed: 2026-06-17 KST
  • Platform: macOS / Apple Silicon

User-visible symptom

After the update, macOS again shows the Gatekeeper-style dialog that Codex Computer Use is damaged and cannot be opened. Korean localized dialog text observed by the user:

Codex Computer use 는 손상되었기 때문에 열 수 없습니다.

Local evidence before repair

The helper did not look actually corrupt on disk:

$ codesign --verify --deep --strict --verbose=2 ~/.codex/computer-use/Codex\ Computer\ Use.app
/Users/kether/.codex/computer-use/Codex Computer Use.app: valid on disk
/Users/kether/.codex/computer-use/Codex Computer Use.app: satisfies its Designated Requirement

$ spctl --assess --type execute --verbose=4 ~/.codex/computer-use/Codex\ Computer\ Use.app
/Users/kether/.codex/computer-use/Codex Computer Use.app: accepted
source=Notarized Developer ID

The bundled source helper inside the updated app also passed:

/Applications/Codex.app/Contents/Resources/plugins/openai-bundled/plugins/computer-use/Codex Computer Use.app: valid on disk
/Applications/Codex.app/Contents/Resources/plugins/openai-bundled/plugins/computer-use/Codex Computer Use.app: satisfies its Designated Requirement
/Applications/Codex.app/Contents/Resources/plugins/openai-bundled/plugins/computer-use/Codex Computer Use.app: accepted
source=Notarized Developer ID

Nested helpers also passed codesign + spctl:

CUALockScreenGuardian.app: valid / accepted / Notarized Developer ID
Codex Computer Use Installer.app: valid / accepted / Notarized Developer ID
SkyComputerUseClient.app: valid / accepted / Notarized Developer ID

Extended attributes did not show com.apple.quarantine on the helper. The local copy only showed:

/Users/kether/.codex/computer-use/Codex Computer Use.app: com.apple.macl:

The bundled source helper had no xattr output.

Process / state evidence

After the update and before repair, several Computer Use processes were still running, including orphaned SkyComputerUseClient instances parented to PID 1, plus a SkyComputerUseService instance and client processes launched through relative ./Codex Computer Use.app/... paths.

There was also a stale IPC lock path present:

~/Library/Group Containers/2DC432GLL2.com.openai.sky.CUAService/IPC/computeruse.sock.lock

Working root-cause hypothesis

This does not appear to be simple app-bundle corruption, signing failure, or notarization failure. The evidence points toward a Computer Use lifecycle/update-state bug:

  1. Codex updates the desktop app and refreshes the Computer Use helper to build 810.
  2. Stale/orphaned SkyComputerUseClient / SkyComputerUseService processes and IPC/cache state survive or are recreated around the update/restart boundary.
  3. macOS then surfaces the helper as "damaged" even though direct codesign and spctl checks accept both the copied helper and the bundled source helper.

Local workaround that fixed this instance

This sequence cleared the problem locally:

pkill -TERM -f '/SkyComputerUse(Client|Service)'
pkill -KILL -f '/SkyComputerUse(Client|Service)'
rm -rf ~/Library/Caches/com.openai.sky.CUAService \
       ~/Library/Caches/com.openai.sky.CUAService.cli \
       ~/Library/Caches/com.openai.codex/org.sparkle-project.Sparkle/Installation \
       ~/Library/Caches/com.openai.codex/org.sparkle-project.Sparkle/Launcher \
       ~/Library/Caches/com.openai.codex/org.sparkle-project.Sparkle/PersistentDownloads \
       ~/Library/Group\ Containers/2DC432GLL2.com.openai.sky.CUAService/IPC
# refresh ~/.codex/computer-use/Codex Computer Use.app from the bundled helper inside /Applications/Codex.app
# re-register with lsregister

After the repair:

Codex Computer Use.app: valid on disk
Codex Computer Use.app: satisfies its Designated Requirement
Codex Computer Use.app: accepted
source=Notarized Developer ID

Then open -n -g ~/.codex/computer-use/Codex\ Computer\ Use.app successfully launched SkyComputerUseService without the damaged-app dialog.

Please investigate the update/restart lifecycle around ~/.codex/computer-use, stale SkyComputerUse* processes, and 2DC432GLL2.com.openai.sky.CUAService IPC/cache cleanup. The recurring symptom is misleading because the app bundle verifies successfully after the dialog appears.

rokgregoric · 1 month ago

Still reproducing on a newer Codex Desktop build.

Environment:

  • Codex Desktop: 26.611.61753
  • Bundle version: 4008
  • Bundled CLI: codex-cli 0.140.0-alpha.19
  • macOS: 26.5.1 build 25F80
  • Architecture: arm64

Observed dialog:

"Codex Computer Use.app" is damaged and can't be opened. You should move it to the Trash.

Additional diagnostics:

$ codesign --verify --deep --strict --verbose=2 /Applications/Codex.app
/Applications/Codex.app: invalid signature (code or signature have been modified)
In architecture: arm64

$ codesign --verify --deep --strict --verbose=2 "/Applications/Codex.app/Contents/Resources/plugins/openai-bundled/plugins/computer-use/Codex Computer Use.app"
/Applications/Codex.app/Contents/Resources/plugins/openai-bundled/plugins/computer-use/Codex Computer Use.app: invalid signature (code or signature have been modified)
In architecture: arm64

$ spctl --assess --type execute --verbose=4 /Applications/Codex.app
/Applications/Codex.app: internal error in Code Signing subsystem

$ spctl --assess --type execute --verbose=4 "/Applications/Codex.app/Contents/Resources/plugins/openai-bundled/plugins/computer-use/Codex Computer Use.app"
/Applications/Codex.app/Contents/Resources/plugins/openai-bundled/plugins/computer-use/Codex Computer Use.app: internal error in Code Signing subsystem

xattr -l on both the main app and nested helper did not show com.apple.quarantine; the main app had com.apple.macl, com.apple.metadata:_kMDItemLastOutOfSpotlightEngagementDate, and com.apple.provenance, while the nested helper had only com.apple.provenance.

This looks like the current installed app/helper bundle is signature-invalid rather than a normal quarantine-only failure.

erickreutz · 1 month ago

Confirming this is an issue for me as well.

GGBondBlueWhale · 1 month ago

Regression after 26.616.41845 auto-update

This issue appears to have regressed again.

Just now, after Codex Desktop updated and restarted automatically, macOS immediately showed the same damaged-app dialog for the Computer Use helper:

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

The dialog also says:

This file was downloaded on an unknown date.

Environment

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

Steps observed

  1. Codex Desktop auto-updated to 26.616.41845.
  2. Codex restarted automatically after the update.
  3. Immediately after restart, macOS showed the damaged-app warning for Codex Computer Use.

Expected behavior

Codex Desktop should update and restart cleanly, and the bundled Codex Computer Use helper should remain usable without any macOS damaged-app / Move to Trash warning.

Actual behavior

Codex Computer Use cannot be opened after the update because macOS reports it as damaged and prompts me to move it to the Trash.

Regression note

This same issue appeared in earlier versions, then seemed to be fixed in the last few builds, but it has now returned after the 26.616.41845 update. Please treat this as a regression and investigate the update/restart lifecycle for the Computer Use helper, especially packaging/signing/notarization/quarantine handling and any stale helper state left across auto-updates.

lily3miller3-arch · 27 days ago

I have the same problem.