Codex auto-update repeatedly triggers persistent syspolicyd/trustd CPU runaway until macOS reboot

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

Codex 26.715.72359, build 5718

What subscription do you have?

Plus

What platform is your computer?

macOS 26.5.1 (25F80), MacBook Pro Mac17,9, M5 Pro

What issue are you seeing?

After every Codex auto-update, syspolicyd uses 215–230% CPU and
trustd uses 60–65% CPU. Logs repeatedly show:

• GK library assessment
• Recording cache miss
• failed to call driver: 0x3

Quitting Codex does not reliably fix it. Rebooting macOS immediately resolves it.

What steps can reproduce the bug?

I can reproduce this issue after Codex Desktop auto-updates. It has occurred after updates on two consecutive days.

1. Start with a normally functioning system.
2. Allow Codex Desktop to install an automatic update.
3. After the update, the fans become very loud and system load increases.
4. syspolicyd and trustd enter a persistent high-CPU state.
5. Fully quitting applications does not resolve the condition.
6. Reboot macOS.
7. CPU usage immediately returns to normal.
8. The same problem recurs following the next Codex update.

What is the expected behavior?

Updating Codex Desktop should not leave macOS Gatekeeper services in a persistent validation loop or require a full system reboot.
Please let me know if additional diagnostics, logs, or a sysdiagnose capture would be useful.

Additional information

This appears specifically correlated with the Codex update process rather than ordinary Codex workloads. Rebooting consistently clears the condition, but it returns after a subsequent Codex auto-update.
The latest affected release, 26.715.72359 build 5718, indicates that the problem is still present as of July 22, 2026.