›_ Codex Issues
Codex Issues / #25973

Computer use and browser plug-in disappear after updating to the latest version for Mac. Version 26.601.20914

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

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

Version 26.601.20914

What subscription do you have?

Max

What platform is your computer?

Mac

What issue are you seeing?

After Codex updated the chat that was before, communicating with another application suddenly constantly showed "reconnecting, reconnecting", but nothing happened in the settings. The computer use was either completely gone, or it said it needs to be installed. The browser plugin sometimes shows, most of the time doesn't, especially after restarting the app. If you click around a bit in the app, for whatever reason they reappear. I attach the screenshots. Please fix.

<img width="751" height="350" alt="Image" src="https://github.com/user-attachments/assets/030f4adc-2d40-40a7-9a4b-7aa1b397dafa" />
<img width="751" height="350" alt="Image" src="https://github.com/user-attachments/assets/11108c3e-0b03-4613-a69b-6355db59de39" />
<img width="751" height="350" alt="Image" src="https://github.com/user-attachments/assets/fce73d94-4485-424b-a62e-9e72fc24f8aa" />
<img width="751" height="350" alt="Image" src="https://github.com/user-attachments/assets/3ddd6253-7f52-4255-bf28-7f3248222c7a" />

What steps can reproduce the bug?

Update to the latest version.

What is the expected behavior?

the computer use disappears or does not work properly try to use another app on the computer in a chat. The chat will constantly tell you to reconnect, reconnect, reconnect.

Additional information

MacBook Pro latest version

View original on GitHub ↗

6 Comments

yellowsnowagency · 1 month ago

Oh, BTW, if you activate or install the plug-in, it just doesn't work. Doesn't matter; we tried it 15 times: uninstalling the app, reinstalling the app, etc. We try to re-install the plugin. It doesn't work. If it appears, even if you uninstall it and re-install it, the browser plugin or the computer-use plugin seem to be disconnected or buggy.

github-actions[bot] contributor · 1 month ago

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

  • #25809
  • #25758
  • #25813

Powered by Codex Action

yellowsnowagency · 1 month ago

We did search for computer use. It didn't show up.

yellowsnowagency · 1 month ago

Okay, we found a workaround. If the computer use plugin appears in the plugin section, we would install it again and then, we would click the "Try it in a chat". I can, on that plugin, then a new chat opens, and this new chat is fully functioning. The computer use plugin works, but the chats that are older and use the computer use plugin still crash. If we go to an older chat, it still shows "reconnect, reconnect, reconnect", but if we go to the new chat, it actually sees the plugin and uses it. We did not restart the app yet, because as we are using it, we don't want to, as now this workaround chat seems to work for now.

jason-chang · 1 month ago

Adding another data point from a macOS 26.5 machine. This looks related to the Computer Use / Browser plugin failures, but the local evidence points to a sandboxed trust-evaluation problem rather than the Codex Computer Use.app bundle actually being damaged.

Environment, with private machine/user paths redacted:

  • macOS 26.5, Darwin 25.5.0, arm64
  • Codex App 26.601.20914, bundle version 3497
  • Bundled Computer Use app path: <Codex.app>/Contents/Resources/plugins/openai-bundled/plugins/computer-use/Codex Computer Use.app

Observed symptom:

  • When Codex invokes Computer Use through tools, macOS shows:
  • "Codex Computer Use.app" is damaged and can't be opened. You should move it to the Trash.
  • The same app can be opened normally outside the Codex tools path.

What I checked:

  1. In a normal/non-sandboxed macOS shell, the app and its helpers validate successfully:
Codex Computer Use.app: valid on disk
Codex Computer Use.app: satisfies its Designated Requirement
Codex Computer Use.app: accepted
source=Notarized Developer ID
origin=Developer ID Application: OpenAI OpCo, LLC (2DC432GLL2)

The same was true for the main executable and bundled helper apps, including:

SkyComputerUseService: accepted
Codex Computer Use Installer.app: accepted
SkyComputerUseClient.app: accepted
CUALockScreenGuardian.app: accepted

A direct LaunchServices open also succeeded:

open -n <Codex Computer Use.app>

and the SkyComputerUseService process started. No new CoreServicesUIAgent / syspolicyd damaged/rejected log entries appeared after that direct open.

  1. In the Codex tool sandbox, the exact same validation commands fail differently:
Codex Computer Use.app: invalid signature (code or signature have been modified)
spctl: internal error in Code Signing subsystem

Even an Apple system app fails in that sandboxed context:

/System/Applications/TextEdit.app: CSSMERR_TP_NOT_TRUSTED

and keychain lookup is broken there:

security list-keychains
security: SecKeychainCopySearchList: One or more parameters passed to a function were not valid.
  1. Running the same checks outside the Codex tool sandbox immediately succeeds:
/System/Applications/TextEdit.app: valid on disk
/System/Applications/TextEdit.app: satisfies its Designated Requirement

security list-keychains
    <user login keychain>
    /Library/Keychains/System.keychain

Conclusion:

The damaged-app dialog appears to be a false Gatekeeper/code-signing failure triggered by the Codex tools sandbox / Computer Use launch context. The bundled app itself is signed and notarized correctly in the normal macOS trust context. Reinstalling or removing quarantine attributes is unlikely to fix this specific failure mode, because com.apple.quarantine was not present and normal spctl/codesign checks pass.

A likely area to inspect is how Codex launches or validates bundled plugins from the tool sandbox, especially whether that sandbox loses access to the normal keychain/trust evaluation context on macOS 26.5.

davibusanello · 1 month ago

I have the same issue, and I noticed that most of the time when the Codex App leaves lingering processes when it exits or is closed, so I suspect it's causing the conflict when there is an app update.