Apple Silicon
Use official
Start with the OpenAI Mac build.
Intel Mac compatibility guide
Codex App on Intel Macs
Pick the right download for your Mac. Apple Silicon should use the official build. Intel Macs need a workaround build.
Official Mac linkDirect Intel ZIPNo mirrored filesBuilt for fast install decisions
Recommended first step
Try the official Mac download first
Best for Apple Silicon Macs.
Intel Mac
Use workaround
Start with the direct Intel build.
If it fails
Check the chip
Most errors here are compatibility issues.
Start here
Decide what to do in under a minute
01
Check your Mac chip
Apple Silicon uses the official build. Intel uses the workaround build.
02
Pick the right download
Choose the direct path first. Use the full releases page only if you want more options.
03
Use the fallback if needed
If you just need Codex working today, use Codex CLI instead of forcing the desktop app.
Quick answer
- No, Codex App is not officially supported on Intel Macs today.
- The core issue is architecture mismatch: the desktop build targets Apple Silicon rather than x86_64 Intel hardware.
- Start with the official Mac download if you are on Apple Silicon. If you are on Intel, use one of the workaround paths below instead of retrying the same installer.
Downloads
All download options in one place
Best for Apple Silicon
Official Codex App
Cleanest path for supported Macs.
- Best starting point for Apple Silicon Macs
- Not the right choice for Intel Macs
Easier Intel workaround
Codex Desktop Rebuild
Intel-friendly desktop download page with release assets.
- Good fit if you want release files instead of scripts
- Community-maintained, so expect some update lag
More technical Intel path
Intel Repackager
Shortest path to trying Codex on an Intel Mac.
- Fastest direct Intel link
- Community-packaged, so update and trust risk still apply
Why it happens
Why Intel Macs hit these errors
This search intent is unusually clear: people try to install Codex App on an Intel Mac, the launch fails, and they immediately look for a reason plus a safe next step. That makes the page more of a compatibility answer page than a general product review.
A recurring point of confusion is Rosetta. Rosetta helps Apple Silicon Macs run Intel software. It does not let an Intel Mac run an Apple Silicon-only desktop build. That one-direction misunderstanding explains why many users keep retrying the installer instead of switching workflows.
Exact-match troubleshooting
The three errors users hit most often
incorrect executable format
This usually means macOS is trying to launch a binary compiled for a different CPU architecture than the machine supports.
Cause
The desktop app package contains an Apple Silicon build, while the Intel Mac expects x86_64-compatible executables.
What to do instead
Stop reinstalling the same app package. Move to Codex CLI or an editor workflow instead of treating the error as a normal install corruption issue.
NSOSStatusErrorDomain -10661
This error appears when the app cannot be opened because the binary format or environment is not valid for the current machine.
Cause
For this keyword cluster, the most likely cause is the same architecture mismatch between Intel hardware and an Apple Silicon-targeted app build.
What to do instead
Treat it as a compatibility issue first. Check Mac architecture, verify official support status, and choose an officially supported workflow.
This Mac is not supported / prohibited symbol
Some users see a direct support warning, while others only see launch failure symptoms. Both point to the same compatibility boundary.
Cause
The app package is not intended for Intel macOS environments, so the operating system blocks or fails the launch.
What to do instead
Use the desktop app only on supported Apple Silicon hardware. On Intel Macs, use the alternatives below and avoid relying on unofficial repackaging unless you fully accept the risk.
Safer path
If you do not want the Intel workaround
Codex CLI
The cleanest fallback when you still want Codex workflows on an Intel Mac.
- Closer to an officially supported developer workflow
- No dependency on the unsupported desktop shell
- Best fit for troubleshooting, automation, and repeatable local use
Editor-based workflow
A practical choice if you mainly want coding assistance inside a familiar environment.
- Avoids the unsupported desktop wrapper
- Keeps the workflow inside tools many developers already use
- Better than chasing binary patches for basic productivity
Unofficial rebuilds or repackagers
These may look attractive for Intel support, but they come with trust, stability, and maintenance risk.
- Not the default recommendation
- May lag behind official releases
- Require stricter trust review before use on a development machine
Status and trust
What is safe to try and what to avoid
Current support status
Current public discussion consistently points to Apple Silicon support for the desktop app, with Intel users finding workarounds mainly through community threads and GitHub issues rather than official product guidance.
- Treat official platform guidance as the source of truth
- Use community projects as references, not default install advice
- Re-check support status before publishing major page updates
Before you install a workaround build
- Check whether you are about to install an official build or a community workaround.
- Do not enter sensitive credentials into a build you do not trust.
- Expect Intel workaround builds to break after upstream updates.
- Prefer the path with the least patching and the clearest release process.
- If reliability matters more than desktop UI, use Codex CLI instead.
FAQ
Questions people search verbatim
Does Codex App work on Intel Mac?
Not as an officially supported desktop app path today. The page intent behind this query is usually compatibility troubleshooting, and the safest answer is to use an alternative workflow instead.
Can Rosetta run Codex App on Intel Mac?
No. Rosetta is commonly misunderstood here. It helps Apple Silicon Macs run Intel apps, not the other way around.
What should I do after seeing incorrect executable format?
Treat it as a platform mismatch, not a normal reinstall problem. Check your Mac architecture and move to a supported workflow such as Codex CLI.