Is damaged and cant be opened
Resolved 💬 11 comments Opened Feb 7, 2026 by smileBeda Closed Feb 27, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of Codex CLI is running?
0.98.0
What subscription do you have?
PRO
Which model were you using?
-
What platform is your computer?
Darwin 25.2.0 arm64 arm
What terminal emulator and version are you using (if applicable)?
Terminal.app
What issue are you seeing?
brew install codex
...codex
<img width="538" height="566" alt="Image" src="https://github.com/user-attachments/assets/7aa695ad-8a67-4be6-b597-1ac704c8a51c" />
What steps can reproduce the bug?
See above
What is the expected behavior?
a working CLI
Additional information
I have the APP installed as well (downloaded from the internet) - not sure if that is related.
11 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Are you able to repro this, or was it a one-time occurrence? I'm wondering whether there was just a download error or interruption.
yes, it is replicable, ever since I try to install/use it.
And then, the screen thing pops up I show in the opening comment.
Are you still seeing this with the latest builds?
Just got it after a fresh macOS 26.3 update from 26.2.
Woraround: Settings ➡️ Security ➡️ Excplicitly allow this binary. You will get this entry in the settings only after seeing the "macOS blocked unsigned softare" alert.
<img width="1651" height="1704" alt="Image" src="https://github.com/user-attachments/assets/357e6383-7add-4ec5-a5c8-de2309dc9f72" />
Started seeing today after standalone codex app update. Reproducible even after brew reinstall.
npm version runs fine
This is not a solution that should be promoted. Also, it is entirely unrelated to the issue reported here.
It works for the case that user experienced (UNSIGNED NOT EQUAL DAMAGED), but there is a reason things are flagged, and ignoring that, makes the entire tool meaningless (Mac's safety guards, not codex)
---
@ushkinaz - I kept trying when it happened to me, and suddenly it worked.
Far shot but are you on a starlink connection? I am, and I suspect it might have to do something with it (dropped packages, something alike that)
@smileBeda good call, but no, I'm not. As far as I know brew uses checksums, so it's probably not connection issues.
Nope, I was wrong, is damaged download cache.
I blame Elon for that damaged cache. Just in case.
@smileBeda haha having the same issue with 0.128.0, have tried all the solutions provided above but no luck, can you help how suddenly it worked. lol