›_ Codex Issues
Codex Issues / #32175

Computer Use helper 26.708.1000366 crashes on macOS 15.7.4 due to missing Swift runtime symbol

Open 💬 2 comments Opened Jul 10, 2026 by JofArnold
💡 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.144.1

What subscription do you have?

Pro

Which model were you using?

gpt-5.6-sol

What platform is your computer?

darwin 24.6.0 arm64 arm

What terminal emulator and version are you using (if applicable)?

iTerm2

Codex doctor report

Redacted

What issue are you seeing?

Codex's Computer Use helper crashes immediately on macOS 15.7.4, and the in-app Browser does not expose a controllable backend.

Prompt used:
"Use Browser to open http://127.0.0.1:5173"

Browser errors:
Browser is not available: iab

Browser backend discovery result:
[]

Computer Use service error, with PII redacted:

dyld[<pid>]: Symbol not found: _swift_task_addPriorityEscalationHandler
Referenced from:
/Users/<redacted>/.codex/computer-use/Codex Computer Use.app/Contents/MacOS/SkyComputerUseService
Expected in:
/usr/lib/swift/libswift_Concurrency.dylib

Environment:

  • macOS 15.7.4 (24G517), Apple Silicon
  • ChatGPT app 26.707.31428
  • Codex Computer Use helper 26.708.1000366
  • Helper LSMinimumSystemVersion: 14.4
  • Helper SDK: macOS 26.4
  • Helper Xcode version: 26.4

Both the helper bundled inside ChatGPT.app and the installed copy under ~/.codex/computer-use fail with the same missing Swift runtime symbol.

What steps can reproduce the bug?

Thread ID:
019f4c21-925a-7fc0-b301-15b95af29647

  1. Use an Apple Silicon Mac running macOS 15.7.4.
  2. Install and launch ChatGPT app 26.707.31428.
  3. Enable the Browser plugin, Browser Use, the in-app Browser, and Computer Use.
  4. Restart ChatGPT.
  5. Start a Codex task and submit:

"Use Browser to open http://127.0.0.1:5173"

  1. Observe that Browser backend discovery returns [] and selecting "iab" reports:

Browser is not available: iab

  1. Launch the bundled helper directly to reproduce the underlying binary failure:

"/Applications/ChatGPT.app/Contents/Resources/plugins/openai-bundled/plugins/computer-use/Codex Computer Use.app/Contents/MacOS/SkyComputerUseService" --help

Alternatively, test the installed copy:

"/Users/<redacted>/.codex/computer-use/Codex Computer Use.app/Contents/MacOS/SkyComputerUseService" --help

Both commands terminate immediately with:

dyld: Symbol not found: _swift_task_addPriorityEscalationHandler
Referenced from: SkyComputerUseService
Expected in: /usr/lib/swift/libswift_Concurrency.dylib

What is the expected behavior?

SkyComputerUseService should launch successfully on macOS 15.7.4 because its bundle declares macOS 14.4 as the minimum supported system version.

It should not reference Swift runtime symbols unavailable on supported macOS versions.

After the service starts, Codex should expose an "iab" Browser backend and successfully open and control http://127.0.0.1:5173.

Additional information

N/A

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 1 month ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #32085
  • #32032

Powered by Codex Action

BravoNiceCatch · 1 month ago

Independent confirmation on the exact same OS and helper build.

Environment:

  • macOS 15.7.4 (24G517)
  • Apple Silicon arm64 (native, not translated)
  • Codex Computer Use / SkyComputerUseService 26.708.1000366 (build 1000366)
  • Bundle ID: com.openai.sky.CUAService
  • Signing team: 2DC432GLL2
  • SIP enabled

A fresh local crash report from 2026-07-11 shows that SkyComputerUseService launched and was terminated by dyld about 42.5 ms later, before any permission handling:

Termination Reason: Namespace DYLD, Code 4 Symbol missing
Symbol not found: _swift_task_addPriorityEscalationHandler
Referenced from: SkyComputerUseService
Expected in: /usr/lib/swift/libswift_Concurrency.dylib
(terminated at launch; ignore backtrace)

The crash report records fatalDyldError: 1, EXC_CRASH / SIGABRT, and an arm64 service image UUID of 61c0b615-7f27-3a07-8d97-77abc7139236.

The user-visible result is Sky Computer Use native pipe startup failed. This is therefore an independent reproduction of the same launch-time binary/runtime incompatibility, not an Accessibility or Screen Recording permission problem. Reinstalling the current helper build does not change the failure.