Computer Use crashes on macOS 15.3 after ChatGPT update: missing _swift_task_addPriorityEscalationHandler

Open 💬 6 comments Opened Jul 11, 2026 by cloverclover-web
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

ChatGPT:26.707.41301,build 5103

What subscription do you have?

Pro

What platform is your computer?

Darwin 24.3.0 arm64 arm

What issue are you seeing?

After updating to the unified ChatGPT desktop app, the bundled Computer Use
plugin can no longer start on macOS 15.3.

Environment:

  • ChatGPT desktop app: 26.707.41301, build 5103
  • Computer Use helper: 26.708.1000366, build 1000366
  • macOS: 15.3 (24D60)
  • Architecture: Apple Silicon arm64
  • uname -mprs: Darwin 24.3.0 arm64 arm

Error returned by Computer Use:

Sky Computer Use native pipe startup failed

Both SkyComputerUseClient and SkyComputerUseService terminate immediately.
The macOS crash report contains:

Termination Reason: Namespace DYLD, Code 4 Symbol missing

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

The processes crash before reaching the Screen Recording or Accessibility
permission checks. Re-enabling those permissions does not affect the failure.

The helper bundle declares LSMinimumSystemVersion 14.4, but it was built using
the macOS 26.4 SDK and references a Swift concurrency symbol that is unavailable
in the macOS 15.3 runtime.

What steps can reproduce the bug?

  1. Use an Apple Silicon Mac running macOS 15.3.
  2. Install or update ChatGPT desktop to version 26.707.41301.
  3. Enable the bundled Computer Use plugin.
  4. Start a new ChatGPT task and invoke @Computer, or initialize the bundled

Computer Use runtime and call sky.list_apps().

  1. Computer Use returns "Sky Computer Use native pipe startup failed".
  2. A new SkyComputerUseClient or SkyComputerUseService crash report appears

under ~/Library/Logs/DiagnosticReports.

Minimal reproduction:

if (!globalThis.sky) {
const { setupComputerUseRuntime } = await import(
"/Users/<username>/.codex/plugins/cache/openai-bundled/" +
"computer-use/1.0.1000366/scripts/computer-use-client.mjs"
);
await setupComputerUseRuntime({ globals: globalThis });
}

await sky.list_apps();

Result:

Sky Computer Use native pipe startup failed

The failure reproduces in a fresh task and does not depend on token usage or
context-window usage.

Session ID: Not applicable / not available.
Token-limit usage: Not applicable.
Context-window usage: Not applicable.

What is the expected behavior?

The bundled Computer Use helper should start successfully on a supported
Apple Silicon Mac running macOS 15.3.

Calling sky.list_apps() should return the available applications, and Computer
Use should proceed to request or verify Screen Recording and Accessibility
permissions instead of crashing during dynamic linking.

If macOS 15 is no longer supported by this helper build, ChatGPT should detect
the incompatible OS version and display a clear compatibility message instead
of reporting a generic native-pipe startup failure.

Additional information

_No response_

View original on GitHub ↗

6 Comments

github-actions[bot] contributor · 9 days ago

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

  • #32310
  • #32210
  • #32175
  • #32085
  • #32032

Powered by Codex Action

AuggyH · 9 days ago

Computer Use plugin crashes at launch on macOS 15.5

Product

  • ChatGPT desktop / Codex
  • Bundled Computer Use plugin

Environment

  • macOS 15.5 (24F74)
  • Apple Silicon, arm64
  • Computer Use plugin package: 1.0.1000366
  • Bundled Computer Use binary version: 26.708.1000366

Reproduction

  1. Initialize Computer Use through the bundled plugin wrapper.
  2. Call the passive sky.list_apps() operation.

No target application is opened and no UI action is attempted.

Actual result

The wrapper returns:

Sky Computer Use native pipe startup failed

Both native processes terminate at launch:

  • SkyComputerUseClient
  • SkyComputerUseService

The macOS crash reports record:

  • Exception: EXC_CRASH / SIGABRT
  • Termination namespace: DYLD
  • Indicator: Symbol missing
  • Missing symbol: _swift_task_addPriorityEscalationHandler
  • Expected library: /usr/lib/swift/libswift_Concurrency.dylib

Expected result

Computer Use should initialize and the passive app-list operation should return without launching or controlling an application.

Reproducibility

100 percent in repeated attempts, including after updating and restarting the desktop app.

Additional checks

  • The bundled Computer Use app exists on disk.
  • Deep and strict code-signature verification passes.
  • The bundle is signed by OpenAI and has a stapled notarization ticket.
  • The host Swift concurrency library does not export the missing symbol.

Impact

Computer Use cannot initialize at all on this host. App enumeration, passive app-state reads, and all later UI operations are unavailable.

Privacy note

This report intentionally excludes usernames, account details, local project names and paths, document or asset names, task identifiers, process identifiers, device identifiers, crash UUIDs, and raw crash-report attachments.

XiaoVai · 9 days ago

Confirmed on another affected Apple Silicon machine.

Environment:

  • Codex desktop app: 26.707.41301 (build 5103)
  • Computer Use helper: 26.708.1000366 (build 1000366)
  • macOS: 15.6.1 (24G90)

Reproduction:

  1. Invoke Computer Use and call sky.list_apps().
  2. It returns Sky Computer Use native pipe startup failed.
  3. Reinstalling the bundled Computer Use component reports success but does not change the failure.

A fresh SkyComputerUseService diagnostic report is generated on every attempt. The launch-time DYLD termination is:

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

This occurs before any Accessibility or Screen Recording permission flow, so it is not a permissions/configuration problem. Please provide a helper build compatible with the macOS 15 Swift runtime, or an explicit compatibility gate.

vincent990291-design · 9 days ago

I can confirm the same regression on another macOS 15.x version.

Environment:

  • MacBook Pro 16-inch 2021 (MacBookPro18,2), Apple Silicon
  • macOS 15.6.1 (24G90)
  • Darwin 24.6.0 arm64
  • ChatGPT/Codex Desktop 26.707.41301, build 5103
  • Computer Use helper 26.708.1000366, build 1000366
  • Helper declares LSMinimumSystemVersion 14.4
  • Helper was built with macOS 26.4 SDK

The latest SkyComputerUseClient crash report shows:

Termination Reason: Namespace DYLD, Code 4, Symbol missing

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

The process terminates at launch before Accessibility or Screen Recording permission checks. Restarting the app and checking permissions do not resolve it.

This confirms that the current helper is also incompatible with macOS 15.6.1, not only macOS 15.3.

TaylorChen · 9 days ago

Confirmed on another affected machine.

Environment:

  • macOS: 15.3.1 (24D70)
  • ChatGPT Mac app: 150.0.7871.115
  • Computer Use plugin: 1.0.1000366
  • Computer Use helper: 26.708.1000366
  • Bundle id: com.openai.sky.CUAService
  • Apple Silicon

Symptoms:

  • Accessibility permissions are enabled for both ChatGPT and Codex Computer Use.
  • sky.list_apps() fails with:

Sky Computer Use native pipe startup failed

Direct helper launch fails with:

dyld: Symbol not found: _swift_task_addPriorityEscalationHandler
Referenced from:
~/.codex/plugins/cache/openai-bundled/computer-use/1.0.1000366/Codex Computer Use.app/Contents/MacOS/SkyComputerUseService
Expected in:
/usr/lib/swift/libswift_Concurrency.dylib

This started after updating Codex/Computer Use. The same machine and permissions worked before the update, so this appears to be a compatibility regression in the new Computer Use helper rather than a permissions issue.

TaylorChen · 7 days ago

I just updated CODEX and gave it a try; the issue has been fixed—that was really fast!