You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
macOS Codex Desktop repeatedly invalidates code signature and triggers syspolicyd/trustd high CPU #28583
Workspace: external volume, /Volumes/STORE N go/IDB
Problem:
After reinstalling Codex Desktop, it works for a while, then macOS starts heating up. Activity Monitor / ps shows syspolicyd and trustd using very high CPU whenever Codex Desktop is open.
/Applications/Codex.app: internal error in Code Signing subsystem
Earlier, the Computer Use helper also showed:
/Users/vhdelgado/.codex/computer-use/Codex Computer Use.app: invalid signature (code or signature have been modified)
I disabled notify, disabled browser@openai-bundled, and blocked ~/.codex/computer-use, so SkyComputerUseService no longer appears. However, the issue still returns with the main /Applications/Codex.app bundle.
Expected:
Codex.app should remain validly signed after installation/update and should not trigger repeated syspolicyd/trustd trust evaluation loops.
Impact:
The machine overheats and Codex Desktop becomes unsafe to keep open for long sessions.
I observe this too: high syspolicyd (>200%) and trustd CPU usage when I have Codex open on my Mac. If it doesn't occur on launch, clicking in the sidebar to open a chat is usually enough to trigger it, but the behavior is not perfectly repeatable, so, despite some effort, I was not able to determine a reliable minimal workaround that would allow continuing to use Codex.
Activity
github-actions commentedon Jun 16, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
malcolmsharpe commentedon Jun 19, 2026
I observe this too: high syspolicyd (>200%) and trustd CPU usage when I have Codex open on my Mac. If it doesn't occur on launch, clicking in the sidebar to open a chat is usually enough to trigger it, but the behavior is not perfectly repeatable, so, despite some effort, I was not able to determine a reliable minimal workaround that would allow continuing to use Codex.