Codex app on macOS triggers syspolicyd/trustd CPU loop and severely slows Xcode and Chrome

Open 💬 4 comments Opened Jun 6, 2026 by Joremando

Summary

The Codex app on macOS appears to trigger a repeated macOS security validation loop involving syspolicyd and trustd.

When Codex is open, my Mac becomes extremely slow. Xcode takes a very long time to run a project, and Chrome becomes unresponsive or freezes. When I completely close Codex, Xcode runs almost immediately again and the high CPU usage from syspolicyd / trustd disappears.

This does not appear to be an Xcode project issue, a hardware issue, or a RAM issue. The slowdown is directly correlated with Codex being open.

Environment

  • Device: Apple Silicon Mac
  • RAM: 128 GB
  • macOS version: [insert macOS version]
  • Codex app version: [insert Codex version if available]
  • Xcode version: [insert Xcode version]
  • Chrome also affected: Yes

Observed behavior

While Codex is open:

  • The whole system becomes very slow.
  • Xcode Run becomes extremely delayed.
  • Chrome freezes or becomes unresponsive.
  • Activity Monitor shows high CPU usage from:
  • syspolicyd
  • trustd
  • WindowServer
  • Codex-related processes are also visible.
  • macOS logs show repeated security validation messages with rapidly increasing PIDs.

Example log output:

syspolicyd [...] [com.apple.syspolicy.exec:default] dispatch_mig_server returned 268435459
syspolicyd [...] <private> with PID 90040 violates validation category policy. This will likely result in a block in the future
syspolicyd [...] SecKeyVerifySignature
syspolicyd [...] SecTrustEvaluateIfNecessary
trustd [...] SecKeyVerifySignature
syspolicyd [...] SecTrustCopyAppleTrustAnchors

syspolicyd [...] <private> with PID 90041 violates validation category policy. This will likely result in a block in the future
syspolicyd [...] <private> with PID 90043 violates validation category policy. This will likely result in a block in the future
syspolicyd [...] <private> with PID 90044 violates validation category policy. This will likely result in a block in the future
syspolicyd [...] <private> with PID 90045 violates validation category policy. This will likely result in a block in the future

The PIDs keep increasing rapidly, suggesting that something related to Codex may be repeatedly launching or validating processes, triggering macOS Gatekeeper / Apple System Policy / trust validation in a loop.

Expected behavior

Codex should not trigger repeated macOS security validation loops or make unrelated apps like Xcode and Chrome unusable.

Actual behavior

With Codex open:

* Xcode Run is severely delayed.
* Chrome becomes unresponsive.
* syspolicyd and trustd consume significant CPU.
* macOS logs show repeated validation events with rapidly increasing PIDs.

With Codex closed:

* Xcode runs almost immediately.
* syspolicyd and trustd disappear from the top CPU list.
* The system returns to normal performance.

Reproduction steps

1. Open Codex app on macOS.
2. Open Xcode.
3. Run an iOS/macOS project.
4. Observe that Xcode Run becomes extremely slow.
5. Open Activity Monitor and sort by CPU.
6. Observe elevated syspolicyd and trustd.
7. Run:

log stream --predicate 'process == "syspolicyd" OR process == "trustd"' --style compact

8. Observe repeated security validation messages with rapidly increasing PIDs.
9. Completely close Codex.
10. Run the same Xcode project again.
11. Xcode runs almost immediately and syspolicyd / trustd CPU usage drops.

Workaround

Closing Codex restores normal Xcode performance.

Attachments

I can provide:

* Activity Monitor screenshot showing syspolicyd and trustd consuming high CPU while Codex is open.
* macOS log output showing repeated syspolicyd validation messages.
* Activity Monitor screenshot after closing Codex, showing normal CPU usage and Xcode running correctly.

View original on GitHub ↗

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