Computer Use 1.0.1000366 crashes on macOS 15.7.5 and appears to disable itself after enable

Open 💬 1 comment Opened Jul 10, 2026 by suyuan2022

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

ChatGPT/Codex Desktop 26.707.31428 (build 5059), with computer-use@openai-bundled plugin 1.0.1000366 and helper 26.708.1000366.

What subscription do you have?

Unknown / not relevant to this local helper startup crash.

What platform is your computer?

Darwin 24.6.0 arm64 arm
macOS 15.7.5 (24G624)
Apple Silicon

What issue are you seeing?

Computer Use does not start even though both the plugin and MCP are enabled. From the user side, enabling Computer Use can appear to turn itself back off after the startup attempt.

The active configuration contains:

[mcp_servers.computer-use]
enabled = true

[plugins."computer-use@openai-bundled"]
enabled = true

The first transport call fails with:

SkyComputerUseTransportError: Sky Computer Use native pipe startup failed
caused by: Sky Computer Use native pipe is unavailable: native pipe path unavailable: No such file or directory (os error 2)

The missing pipe is only a secondary symptom. Unified logging shows LaunchServices successfully launches com.openai.sky.CUAService, but the service runs for about 24 ms and exits with status 6:

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

A fresh SkyComputerUseService crash report is generated on every attempt.

What steps can reproduce the bug?

  1. Run ChatGPT/Codex Desktop 26.707.31428 on macOS 15.7.5 Apple Silicon.
  2. Enable computer-use@openai-bundled and the computer-use MCP.
  3. Restart the app/session so MCP configuration is reloaded.
  4. Initialize the plugin-owned Computer Use wrapper.
  5. Call the minimal transport method:
await sky.list_apps();
  1. Observe Sky Computer Use native pipe startup failed and a new launch-time crash report.

The failure reproduced repeatedly with the same error and crash signature.

What is the expected behavior?

Computer Use should run on the declared deployment target, or Codex should display an explicit macOS/runtime compatibility error without silently reverting or appearing to disable the setting.

Additional information

Local validation:

  • codesign --verify --deep --strict passes.
  • Gatekeeper accepts the helper as a notarized Developer ID app.
  • The helper architecture is arm64, matching the host.
  • LC_BUILD_VERSION declares minimum macOS 14.4 and SDK 26.4.
  • nm -u confirms that _swift_task_addPriorityEscalationHandler is imported.
  • Accessibility and Screen Recording permissions cannot affect this failure because the process terminates during dynamic linking.
  • Restarting the session or re-enabling the MCP cannot repair the incompatible binary.

This appears related to #22822 and #32032. The underlying Swift back-deployment bug was fixed upstream in swiftlang/swift#88428, which says the task priority escalation runtime functions had incorrect availability and caused crashes in back-deployed programs.

Please ship a macOS 15-compatible Computer Use helper rebuilt with the Swift availability fix, bundle the required runtime compatibility support, or add an explicit OS compatibility gate. A signed rollback-compatible helper would also unblock affected users while a new build is prepared.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗