Codex Computer Use helper crashes on macOS 14.x: SkyComputerUseClient built with minos 15.0
What happened?
Codex Desktop repeatedly triggers a macOS crash report for SkyComputerUseClient, the bundled Computer Use helper. The helper exits immediately during dynamic linking before a useful app-level backtrace is available.
Expected behavior
Codex should either run the Computer Use helper on supported macOS versions, or avoid launching it / show a clear unsupported-OS message when the current OS is below the helper's minimum supported version.
Actual behavior
On macOS 14.4, the helper fails at launch with a dyld missing-library error:
Termination Reason: Namespace DYLD, Code 1 Library missing
Library not loaded: /usr/lib/swift/libswift_errno.dylib
Referenced from: Codex Computer Use.app/.../SkyComputerUseClient
Reason: tried /usr/lib/swift/libswift_errno.dylib and Preboot Cryptex path, but the library was not found / not in dyld cache
The crash report also states that SkyComputerUseClient was built for macOS 15.0 which is newer than running OS.
Environment
- Codex Desktop:
26.422.71525(build2210) - Affected helper:
com.openai.sky.CUAService.cli, version1.0(build758) - OS: macOS
14.4 (23E214) - Architecture: Apple Silicon / arm64
Local verification
$ sw_vers
ProductVersion: 14.4
BuildVersion: 23E214
$ ls /usr/lib/swift/libswift_errno.dylib
No such file or directory
$ otool -l .../SkyComputerUseClient | rg -A4 'LC_BUILD_VERSION'
cmd LC_BUILD_VERSION
platform 1
minos 15.0
sdk 26.1
$ otool -L .../SkyComputerUseClient
... /usr/lib/swift/libswift_errno.dylib ...
Notes
This appears to be a compatibility / minimum OS mismatch in the Codex Desktop app bundle. Users on macOS 14.x can get repeated crash popups whenever Codex tries to launch the bundled Computer Use helper.
I am intentionally not attaching the full crash report because it contains local usernames, full local paths, process IDs, incident IDs, crash UUIDs, and other machine-identifying details. I can provide a further sanitized excerpt if needed.
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗