Troubleshooting guide
If you are seeing NSOSStatusErrorDomain -10661, the issue is usually not random.
On Intel Mac, this error often shows up when the desktop app path and the machine architecture do not line up.
Do not keep guessing. Work out what the error means first, then choose the next step that fits your machine.
Do this first
Context
The -10661 code can look generic on its own. In Intel Mac setups, it usually points to architecture mismatch between your machine and the installed app binary.
If your error says incorrect executable format instead, open that guide for the right fix steps.
References
The Codex app documentation describes macOS availability for Apple Silicon, which matches the Intel mismatch pattern behind this error.
Issue #12941 reports Intel x86_64 hardware receiving an arm64 Codex.app, then failing with NSOSStatusErrorDomain -10661 at launch.
Issue #12941 was linked to the main Intel desktop support request (#10410), which is still open as of 2026-03-12.
Apple states Rosetta translates Intel apps on Apple Silicon Macs. It does not make Intel Macs run Apple Silicon-only apps.
Related guides
Related guide
Get a direct yes-or-no answer, then choose the safest install path for Intel Mac users.
Related guide
Compare CLI, Cursor or VS Code workflows, source builds, and community app packages for older Intel Macs.
Related guide
Identify architecture mismatch quickly and move to a workflow that actually works on Intel hardware.
Start guide
Go back for download options, chip checks, and step-by-step troubleshooting.
FAQ
Usually not for this scenario. On Intel Macs it is more often a compatibility problem than a missing permission toggle.
Rarely. If architecture is wrong for your device, reinstalling the same bundle does not remove the mismatch.
Check chip architecture, stop reinstall loops, and move to a supported workflow path such as CLI.