Computer Use plugin cause macos crush

Open 💬 2 comments Opened Jun 21, 2026 by thisisgpy

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

26.616.51431

What subscription do you have?

Pro5X

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

After enabling Computer Use for the Codex App, the macOS system experienced recurring high CPU usage and file descriptor (fd) exhaustion due to syspolicyd. During the failure, syspolicyd held approximately 2540 fds pointing to /Applications/Codex.app/Contents/MacOS/Codex and logged errors such as "Too many open files," "Failed to open main executable for hashing," "Failed to call driver: 0x3," and "SecStaticCode" failure. Subsequently, manually launching apps like Chrome and TikTok from the Dock/Finder resulted in continuous pop-ups but no opening. Disabling the Computer Use UI switch did not completely resolve the issue.

The following were found installed on this machine by Computer Use:

  • /Library/Security/SecurityAgentPlugins/CodexComputerUseAuthorizationPlugin.bundle
  • AuthorizationDB right: com.openai.sky.CUAService.AuthorizationPlugin.remote
  • This right is referenced in the system.login.screensaver rule
  • The com.openai.sky.CUAService Accessibility permission exists in TCC.

It is speculated that the system-level integration of Computer Use/locked-use triggers syspolicyd to repeatedly evaluate the Codex bundle in a specific macOS environment, eventually causing syspolicyd file descriptor exhaustion, which in turn affects the Gatekeeper startup evaluation of other apps.

macOS:

  • ProductVersion: 26.5.1
  • BuildVersion: 25F80

Codex App:

  • CFBundleIdentifier: com.openai.codex
  • CFBundleShortVersionString: 26.616.51431
  • CFBundleVersion: 4212

Computer Use:

  • com.openai.sky.CUAService
  • plugin version observed: 829

What steps can reproduce the bug?

  1. Open Codex app
  2. Enable Computer Use
  3. Do nothing
  4. Crushed

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗