Can't open app in Tahoe 26.2 (25C56)

I can confirm the same issue on my machine.

macOS: 26.2 (Tahoe)
Hardware: Apple Silicon (M-series)
Codex.app: latest

Symptoms:

• App launches (dock icon bounces), but no window appears.
• GUI hangs on startup.
• Running from Terminal shows repeated crashpad errors:

mach_port_request_notification: (os/kern) invalid capability (20)

Notes:

• App is notarized and codesign verifies OK.
• Happens even on a fresh macOS user account.
• --disable-crash-reporter / --no-crashpad flags do not prevent crashpad from starting.

Looks like a Crashpad ↔ macOS 26.2 regression.

Were you able to run earlier versions of the Codex app, or is this the first time you've tried running it on your system? I'm trying to determine if this was a recent regression that we introduced (or perhaps a corrupt image).

Were you able to run earlier versions of the Codex app, or is this the first time you've tried running it on your system? I'm trying to determine if this was a recent regression that we introduced (or perhaps a corrupt image).

Hi,
this is the first time I’ve tried running the Codex app on this system, so I can’t compare it with earlier versions here.

On this same machine, I also tested by creating a brand-new macOS user account. In that case, Codex still fails to start, but with a different error. The app shows the following message:

“Failed to spawn Codex CLI at
/Applications/Codex.app/Contents/Resources/codex”

!Image

At the same time, on another MacBook with the same Apple Silicon hardware and the same macOS version (26.2 Tahoe) — my wife’s laptop — Codex launches and works normally.

This suggests the issue is machine-specific, not related to the user profile, and not a general incompatibility with Apple Silicon or macOS 26.2.

Please let me know if you’d like me to collect any additional logs or diagnostics.

Were you able to run earlier versions of the Codex app, or is this the first time you've tried running it on your system? I'm trying to determine if this was a recent regression that we introduced (or perhaps a corrupt image).

Same for me -- first time I tried running it. I downloaded it yesterday morning at around 9:30a ET, and it's been happening ever since, even when I uninstall and try to download and install (what I assume are) new versions.

Mac Pro - Tahoe 26.2. the same problem. This SW is not supported for this Mac... v

Did you have a copy of the Codex CLI installed on your machine previously? I'm wondering whether you have a stale ~/.codex/config.toml file left on your system. Check for that and delete (or rename) that file if it exists.

Did you have a copy of the Codex CLI installed on your machine previously? I'm wondering whether you have a stale ~/.codex/config.toml file left on your system. Check for that and delete (or rename) that file if it exists.

@etraut-openai Sadly, no—I had only ever used Codex on the web. I did just attempt to reinstall Codex with version 260205.0946 (552), and the Applications folder is now showing up on the .dmg installation screen, but unfortunately it's still entering the same endless loop and becoming unresponsive.

The app still hangs indefinitely at startup with no UI, bouncing dock icon, near-zero CPU usage. The main thread across both is consistently blocked in:

ElectronMain
→ v8::ScriptCompiler::StartConsumingCodeCacheOnBackground
→ node::LoadEnvironment
→ node::StartExecution
→ uv_run / kevent

Once again, sending SIGINT (Ctrl-C) immediately allows startup to continue, which might suggest a V8 interrupt / code-cache deadlock during Electron bootstrap.

In my case I had installed Codex under a different user user0 and the CLI app was only permissioned for that user

-r-x------ 1 user0 admin 54014976 Feb  6 10:09 /Applications/Codex.app/Contents/Resources/codex

But Codex fails when I use it under user1's account.

Seems to just be a permissions issue. I didn't set these permissions though.

Maybe the file just needs a chmod g+rx?

same issue Macbook Air M4 Tahoe 26.2

same issue with Tahoe 26.2 but the codex icon is marked with X

also experiencing this issue on Tahoe 26.2 with Codex 260205.1301.

i've uninstalled my previous CLI installation via brew, backed up and deleted all app/user state for Codex, and restarted my machine. still results in Codex.app becoming unresponsive when opened from the app icon and spotlight.

however, launching from the terminal as @everythingistk mentioned did bring up the Codex window and allow me to login without ctrl+c. subsequent app opens from app icon and spotlight still result in application not responding unless opened via terminal.

so terminal invocation might provide a workaround until this is resolved.

Thanks for the reports. We think we know what is happening here. Our hypothesis (which we had an internal reproduction for) involved user shell startup execing a sub-shell or any other interactive process that causes the root exec to hang indefinitely (asciinema in this case). We will be rolling out a build later today that hydrates the user shell without interactive set which resolved the internal report of this.

Once this rolls out (the build will have 20260209 in it), please confirm if it resolves your issue 🙏

EDIT: removing interactive has other intentional side effects such as not picking up CODEX_HOME in .zshrc. We're going to look into other workarounds but in the meantime, could you try checking your zshrc or zshev for things that might be blocking shell startup such as asciinema and see if removing them fixes this?

In my case I had installed Codex under a different user user0 and the CLI app was only permissioned for that user `` -r-x------ 1 user0 admin 54014976 Feb 6 10:09 /Applications/Codex.app/Contents/Resources/codex ` But Codex fails when I use it under user1's account. Seems to just be a permissions issue. I didn't set these permissions though. Maybe the file just needs a chmod g+rx`?

I'm trying to use it across multiple user accounts too and this is my problem. First I ran it on my personal account and it worked fine, but I can't use it on my work account. This is a pretty big blocker for me.

% ls -la /Applications/Codex.app/Contents/Resources/codex
-r-x------ 1 samsonjs admin 54853856 Feb  9 07:16 /Applications/Codex.app/Contents/Resources/codex*
% whoami
work

I found that running sudo chmod g+rx .../codex fixed the problem for me.

Sent from Proton Mail for Android.

-------- Original Message --------
On Wednesday, 02/11/26 at 08:08 Sami Samhuri @.***> wrote:

samsonjs left a comment (openai/codex#10627) > In my case I had installed Codex under a different user user0 and the CLI app was only permissioned for that user > > -r-x------ 1 user0 admin 54014976 Feb 6 10:09 /Applications/Codex.app/Contents/Resources/codex > > But Codex fails when I use it under user1's account. > > Seems to just be a permissions issue. I didn't set these permissions though. > > Maybe the file just needs a chmod g+rx? I'm trying to use it across multiple user accounts too and this is my problem. First I ran it on my personal account and it worked fine, but I can't use it on my work account. This is a pretty big blocker for me. % ls -la /Applications/Codex.app/Contents/Resources/codex -r-x------ 1 samsonjs admin 54853856 Feb 9 07:16 /Applications/Codex.app/Contents/Resources/codex % whoami work — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.**>

There were at least two issues that contributed to this problem. The first is addressed in the release we just published (602). The second, which affects systems with multiple user accounts, will be addressed in the next release.

A big thanks to everyone who reported these issues and provided clues and repros.

Pleasure to be of assistance

Sent from Proton Mail for Android.

-------- Original Message --------
On Wednesday, 02/11/26 at 13:54 Eric Traut @.***> wrote:

etraut-openai left a comment (openai/codex#10627) There were at least two issues that contributed to this problem. The first is addressed in the release we just published (602). The second, which affects systems with multiple user accounts, will be addressed in the next release. A big thanks to everyone who reported these issues and provided clues and repros. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

Once this rolls out (the build will have 20260209 in it), please confirm if it resolves your issue 🙏 EDIT: removing interactive has other intentional side effects such as not picking up CODEX_HOME in .zshrc. We're going to look into other workarounds but in the meantime, could you try checking your zshrc or zshev for things that might be blocking shell startup such as asciinema and see if removing them fixes this?

Okay, got it working with v260210.1703.

At first, the app was still hanging on launch.

I isolated it to my .zshrc. Codex was executing .zshrc during startup in a non-interactive context. I don’t have asciinema, but I do initialize nvm, modify PATH, and define aliases there. With the normal .zshrc, Codex consistently hangs on launch (Finder, Spotlight, and Terminal).

If I remove or rename .zshrc, Codex launches normally.

Adding this guard at the very top of .zshrc fixes the issue without removing anything else:

[[ -o interactive ]] || return
[[ -t 0 && -t 1 && -t 2 ]] || return

After that, Codex launches normally every time. Thanks for looking into this, and happy to test future releases.

> Once this rolls out (the build will have 20260209 in it), please confirm if it resolves your issue 🙏 > EDIT: removing interactive has other intentional side effects such as not picking up CODEX_HOME in .zshrc. We're going to look into other workarounds but in the meantime, could you try checking your zshrc or zshev for things that might be blocking shell startup such as asciinema and see if removing them fixes this? Okay, got it working with v260210.1703. At first, the app was still hanging on launch. I isolated it to my .zshrc. Codex was executing .zshrc during startup in a non-interactive context. I don’t have asciinema, but I do initialize nvm, modify PATH, and define aliases there. With the normal .zshrc, Codex consistently hangs on launch (Finder, Spotlight, and Terminal). If I remove or rename .zshrc, Codex launches normally. Adding this guard at the very top of .zshrc fixes the issue without removing anything else: `` [[ -o interactive ]] || return [[ -t 0 && -t 1 && -t 2 ]] || return `` After that, Codex launches normally every time. Thanks for looking into this, and happy to test future releases.

Confirmed that this worked for me