Computer Use 1.0.1000366 crashes at launch on macOS 15.7.7 due to missing Swift Concurrency symbol
Summary
Computer Use fails to start on macOS 15.7.7 even when the bundled plugin is enabled and Codex has been restarted.
The native helper exits before MCP/UI control can initialize because dyld cannot resolve a Swift Concurrency symbol from the system runtime.
This appears related to #22822, but it affects the newer Computer Use build 26.708.1000366 / plugin 1.0.1000366, not the older 1.0.791 build reported there.
Environment
- Hardware: Apple Silicon (
arm64, Mac14,2) - macOS: 15.7.7 (24G720)
- Codex app bundle ID:
com.openai.codex - Codex app version:
26.707.31428 - Computer Use plugin version:
1.0.1000366 - Computer Use helper version:
26.708.1000366
The same helper version is present in the app-bundled plugin, the bundled plugin cache, and ~/.codex/computer-use/Codex Computer Use.app.
Steps to reproduce
- Run Codex Desktop on macOS 15.7.7.
- Enable the bundled Computer Use plugin / MCP.
- Start a new Codex session or restart Codex Desktop.
- Invoke any Computer Use action, for example
get_app_statefor the Dock.
Actual result
Computer Use fails before it can read or control the UI. The client reports:
Sky Computer Use native pipe startup failed
A fresh crash report is generated on every attempt. Example crash excerpt, with local paths redacted:
app_name: SkyComputerUseClient
timestamp: 2026-07-10 13:11:08 +0800
app_version: 26.708.1000366
os_version: macOS 15.7.7 (24G720)
termination:
namespace: DYLD
indicator: Symbol missing
reason:
Symbol not found: _swift_task_addPriorityEscalationHandler
Referenced from: SkyComputerUseClient
Expected in: /usr/lib/swift/libswift_Concurrency.dylib
Restarting Codex Desktop and re-enabling the MCP do not help.
Expected result
Computer Use should start and expose working UI-control tools on supported macOS 15.7.x systems, or Codex should clearly report that this helper build is unsupported instead of failing during startup.
Notes
- This is not an Accessibility or Screen Recording permission failure: the helper dies at dynamic-link time, before UI interaction can begin.
- The symptom and missing symbol match #22822, but the affected helper is now
26.708.1000366, so this may be a regression or an unresolved compatibility issue in newer builds. - A compatible helper build, bundled Swift runtime dependency, or explicit macOS compatibility gate would resolve the failure.
23 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I reviewed #31180 and believe this is related but not a duplicate.
#31180 affects an Intel Mac on macOS 12.5.1 and fails while loading
sky.nodebecause of a missing Foundation symbol.This issue affects Apple Silicon on macOS 15.7.7. The bundled Computer Use helper
26.708.1000366crashes at launch with a missing Swift Concurrency symbol:_swift_task_addPriorityEscalationHandlerThe affected architecture, macOS version, failing component, missing symbol, and user-visible behavior are all different. I believe this should remain open as a separate macOS 15.7.7 compatibility/regression report.
Same Issue here
Same here
Confirmed on my machine with the same root cause.
Environment
SkyComputerUseClientLC_BUILD_VERSION: minimum macOS 14.4, SDK 26.4User-visible failure
Computer Use initialization fails on the first transport call with:
The Computer Use MCP server is then automatically written back as
enabled = false.Direct reproduction
Launching
SkyComputerUseClient mcpdirectly fails before the native pipe can be created:Validation
codesign --verify --deep --strictpasses for both the outer Computer Use app and the nested client app.spctlaccepts both as notarized Developer ID applications.This confirms that the missing native pipe is a secondary symptom. The helper crashes because the current build references a Swift Concurrency symbol unavailable on macOS 15.7.4.
A macOS 15-compatible helper build or an explicit compatibility gate would be appreciated.
same issue with mine
⚠ MCP client for computer-use failed to start: MCP startup failed: No such file or directory (os error 2)
⚠ MCP client for event-stream failed to start: MCP startup failed: handshaking with MCP server failed: connection closed: initialize response
⚠ MCP startup incomplete (failed: computer-use, event-stream)
ery confused
Confirmed on another Apple Silicon machine, including the regression timeline.
Environment
Mac14,12, arm64)Failure
The first Computer Use transport call fails with:
The generated
SkyComputerUseServicecrash report shows a launch-time DYLD failure:The helper's
LC_BUILD_VERSIONreports minimum macOS 14.4 and SDK 26.4, but the symbol is a non-weak import.Regression signal
Computer Use worked on this same machine and macOS version a few days earlier. The desktop app was automatically updated on July 10, after which Computer Use stopped starting. Sparkle automatic checks and automatic updates were enabled.
Validation
This extends the report to macOS 15.6.1 and strongly suggests a regression in the newly bundled helper rather than a permissions problem. A signed macOS 15-compatible helper build or an official rollback path would be appreciated.
same issue for me
I can confirm this issue on another Apple Silicon Mac.
My Environment:
26.707.31428(build5059)1.0.100036626.708.1000366arm64Additional reproduction evidence:
24C101).24G720) and rebooted.``
text
``textSky Computer Use native pipe startup failed
5.Launching SkyComputerUseService directly still exits immediately:
dyld: Symbol not found: _swift_task_addPriorityEscalationHandler
Referenced from: SkyComputerUseService
Expected in: /usr/lib/swift/libswift_Concurrency.dylib
I reproduced this and created a working local workaround.
Environment
Diagnosis
SkyComputerUseServicecrashed immediately because it referenced:That symbol was unavailable in
/usr/lib/swift/libswift_Concurrency.dylibon macOS 15. The helper therefore never started its IPC service.Workaround
@oai/skyruntime because the older helper usesCodexComputerUseIPC-1, while the current client defaults to IPC-2.Validation
list_appsreturned 31 applications.get_app_statesuccessfully inspected Safari.https://www.apple.com, and press Return.This is only a local compatibility workaround. The proper upstream fix appears to be rebuilding the current helper so it does not depend on a macOS 26-only Swift concurrency symbol, while keeping the helper and JavaScript client on matching IPC versions.
Reproduced on another Apple Silicon Mac with the same launch-time failure.
Environment:
Both
SkyComputerUseClientandSkyComputerUseServicegenerate fresh crash reports and abort before permission checks:The previous service instance exited normally immediately before the update; the first launch of the updated helper failed. Code signatures verify successfully, and Gatekeeper accepts the notarized binaries. No raw crash report is attached because it contains private identifiers.
Same failure here on a nearby macOS 15.7.x build.
Environment:
Observed from Codex:
Directly launching the bundled helper fails before any Accessibility / Screen Recording permission checks can matter:
Output:
Additional checks:
The same crash reproduces for the helper copied under
~/.codex/computer-use/..., so this does not look like a stale per-user install. The fresh helper bundled inside/Applications/ChatGPT.appfails the same way.codesign -dvon the helper reports:This appears to be the same Swift Concurrency runtime compatibility issue as reported above, affecting macOS 15.7.4 as well as 15.7.7.
Confirmed independently on another affected macOS 15.x system.
Environment
MacBookPro17,1, arm64)15.7.3 (24G419)26.707.31428(build5059)1.0.100036626.708.1000366Reproduction and root cause
sky.list_apps()surfaced:Running the bundled client directly, and separately launching the bundled service, both abort during dynamic linking:
The helper declares minimum macOS
14.4but was built with SDK26.4. This occurs before Accessibility or Screen Recording permissions can matter. Reinstalling, toggling the MCP, and restarting Codex cannot resolve this failure.Verified user-local workaround
I verified a rollback to the previous official Computer Use bundle from Codex Desktop
26.623.141536. That bundle contains Computer Use build857and does not import the missing Swift symbol.The important compatibility detail is to use the older MCP client and older service together. Configuring Codex to launch the old
SkyComputerUseClient mcpdirectly avoids pairing the old service with the current incompatible client/runtime.This workaround:
/Applications/ChatGPT.appAnother Codex instance can perform it as follows:
``
text
``https://persistent.oaistatic.com/codex-app-prod/Codex-darwin-arm64-26.623.141536.zip
``
text
``Codex.app/Contents/Resources/plugins/openai-bundled/plugins/computer-use/
For example:
``
bash
``unzip -q "$ZIP" 'Codex.app/Contents/Resources/plugins/openai-bundled/plugins/computer-use/*' -d "$EXTRACT_DIR"
``
text
``~/.codex/config.toml
~/.codex/computer-use/Codex Computer Use.app
~/.codex/plugins/cache/openai-bundled/computer-use/1.0.1000366/Codex Computer Use.app
Codex Computer Use.appbundles above with the extracted build-857 app. Preserve executable permissions;dittoworks on macOS.[mcp_servers.computer-use]block with an absolute-path direct MCP configuration (replace/Users/YOUwith the real home directory):``
toml
``[mcp_servers.computer-use]
command = "/Users/YOU/.codex/computer-use/Codex Computer Use.app/Contents/SharedSupport/SkyComputerUseClient.app/Contents/MacOS/SkyComputerUseClient"
args = ["mcp"]
cwd = "/Users/YOU/.codex/computer-use"
enabled = true
If
SKY_CUA_SERVICE_PATHis already present under[mcp_servers.node_repl.env], point it at:``
text
``/Users/YOU/.codex/computer-use/Codex Computer Use.app
list_appsfollowed byget_app_state.Validation
With the installed fallback, I verified:
initializesucceedstools/listexposes the complete Computer Use toolsetlist_appssucceedsget_app_state({ app: "Calculator" })returns the Calculator accessibility tree and screenshotThe broken
26.708.1000366bundle and original config remain available in the timestamped backup for rollback. A future Computer Use update may replace this compatibility pin, so the correct upstream fix is still a macOS 15-compatible build (or bundled Swift runtime / accurate OS gate).Additional confirmation for #32032 from Apple Silicon macOS 15.6.1 (24G90):
Computer Use 1.0.1000366 / Sky 26.708.1000366 crashes both the service and
client in dyld before main. I found 73 local Sky crash reports with the same
missing _swift_task_addPriorityEscalationHandler symbol. The only unresolved
strong Swift imports on macOS 15 in both binaries are the add/remove priority
escalation handlers.
This matches swiftlang/swift#88428 (commit 0218eb610ef), the Swift compiler fix
for incorrect back-deployment of withTaskPriorityEscalationHandler. The affected
helper was built with Swift 6.3; the fix is in Swift 6.4. Rebuilding both private
helper targets with the fixed toolchain (and retaining the macOS 26 availability
guard) should repair the declared macOS 14.4 deployment support.
As a temporary validation, I installed the matched Computer Use build 857
client/service from OpenAI's signed and notarized 26.623.141536 arm64 archive.
MCP initialization, list_apps, Calculator state capture, and an actual click all
succeeded on macOS 15.6.1. I did not install or distribute a re-signed binary.
Confirmed on another affected Apple Silicon system. The issue persists in the newer current desktop build.
Environment
26.707.41301(build5103)1.0.100036626.708.1000366(build1000366)15.6.1 (24G90)uname -mprs:Darwin 24.6.0 arm64 armReproduction
Initializing the bundled Computer Use runtime and calling
sky.list_apps()consistently returns:The corresponding sanitized
SkyComputerUseServicecrash report shows that it terminates at launch:A
SkyComputerUseClientcrash report shows the same missing symbol.Troubleshooting already attempted
None of these changed the failure.
codesign --verify --deep --strictpasses, and Gatekeeper accepts the downloaded DMG as a notarized OpenAI Developer ID build. Unified logging also emits repeated application-group entitlement/provisioning warnings forcom.openai.sky.CUAService; however, the crash report establishes the immediate observed failure as the missing Swift Concurrency symbol during DYLD launch, before Screen Recording or Accessibility checks can matter.This confirms that helper
26.708.1000366remains incompatible with at least macOS15.6.1in desktop build26.707.41301.Confirmed on another Apple Silicon Mac, with the newer unified ChatGPT desktop build.
Environment
User-visible failure
Both
sky.list_apps()andsky.get_app_state(...)fail with:Resetting the Computer Use runtime and restarting ChatGPT do not change the result.
Direct reproduction
Launching either bundled native executable directly fails before the native pipe or permission checks can initialize:
Both processes terminate with exit code 134. The macOS 15.6 system Swift Concurrency library does not export the required symbol.
Validation
codesign --verify --deep --strict.Codex Computer Use Installer statusreportsOK: installed.LSMinimumSystemVersion=14.4, but was built with the macOS 26.4 SDK.SkyComputerUseServiceprocess is created, so Accessibility and Screen Recording permissions are not involved in this failure.OpenAI's published ChatGPT macOS requirements still state macOS 14+ on Apple Silicon:
https://help.openai.com/en/articles/9395554-what-are-the-system-requirements-for-the-chatgpt-macos-app
A signed helper rebuilt for the declared deployment target, or an official rollback path, would resolve the blocker.
Adding another data point — this reproduces even on a completely fresh install with zero prior state:
macOS: [run
sw_vers -productVersion]ChatGPT/Codex app: [version from About dialog — post July 9 Codex→ChatGPT merge]
Fully removed all prior install state (app bundle, caches, app support data, TCC grants for com.openai.codex) before reinstalling from scratch. First-run setup completes normally, but the Accessibility/Screen Recording permission prompt never fires at all, and Computer Use fails immediately with "native pipe startup failed" on every target app tested (Notes, Spotify).
This matches the code-signing invalid helper root cause described above — the permission prompt likely never fires because the helper is being killed by launch constraint validation before it can request permissions in the first place.
Same problem here.
Additional reproduction and rollback testing from another affected Apple Silicon Mac:
Environment
Current helper failure
Calling
sky.list_apps()consistently returns:Unified logging shows that Launch Services successfully spawns
SkyComputerUseService, but it exits after approximately 37 ms with:This occurs before Screen Recording or Accessibility permissions can affect the request.
Signed rollback viability
I also tested extracting Computer Use 1.0.758 from the official Codex Desktop 26.422.71525 arm64 package.
list_appscall fails with:Therefore, plugin-only rollback is not a safe or complete workaround. Community workarounds that re-sign the entire parent application materially change its trust and entitlement model.
Requested fix
Please provide one of the following:
A signed rollback helper would immediately unblock macOS 15 users without requiring them to weaken or replace application signing.
Thank you for reporting this issue, we understand the problem here and are working on a hotfix! We'll update this issue when it is released.
I have also met this problem
Environment
26.707.413011.0.100036626.708.100036615.7.7(24G720)arm64)Calling
sky.list_apps()fails with:The underlying cause is that both
SkyComputerUseServiceandSkyComputerUseClientterminate during dynamic linking:Additional checks:
codesign --verify --deep --strictsucceeds.26.708.1000366and have identical service binary hashes.helper terminates before permission checks or UI interaction.
notify = [.../SkyComputerUseClient, "turn-ended"]causes anadditional client crash at the end of a turn, but removing it does not fix the
independently crashing service.
component had been updated.
This confirms that the problem remains present in Codex Desktop
26.707.41301, not only the earlier app build reported above.Update: the hotfix appears to resolve this for me on the same macOS 15 line.
Environment:
Validation after updating:
sky.list_apps()succeeds and returned 24 applications.sky.get_app_state({ app: "com.apple.finder" })succeeds, returning both a Finder accessibility tree and screenshot.This is a successful retest of the formerly failing native-pipe path; the prior
Sky Computer Use native pipe startup failed/ missing_swift_task_addPriorityEscalationHandlererror no longer reproduces for me on macOS 15.7.7.Confirmed fixed after updating to the latest build on the same affected machine.
Environment
Validation
list_appssucceeded and returned the installed applications.get_app_statesuccessfully read the Calculator accessibility tree and captured a screenshot.1succeeded, and the updated input value was read back as1.Sky Computer Use native pipe startup failederror no longer occurs._swift_task_addPriorityEscalationHandler.The hotfix resolves the issue for me. Thank you!