Hacker News new | ask | show | jobs
by williamjinq 8 hours ago
Same here.

I asked Fable to dig into the logs and do a deep research for relevant evidence:

Related reports counted hundreds of Gatekeeper denials for Codex’s own main executable, eventually exhausting syspolicyd file descriptors and causing unrelated notarized apps to be reported as “damaged”:

https://github.com/openai/codex/issues/25882 https://github.com/openai/codex/issues/28071

Quitting Codex and restarting syspolicyd is only a temporary recovery. The useful upstream action is to identify the launch/update/watchdog caller, add exponential backoff plus a hard retry cap, and publish the first known-fixed desktop build.