Skip to content

SkyComputerUseClient unexpectedly exited #18549

Open
Open
SkyComputerUseClient unexpectedly exited#18549
Labels
appIssues related to the Codex desktop appbugSomething isn't workingcomputer-usetool-callsIssues related to tool calling

Description

@tangxiaonian
tangxiaonian
opened on Apr 19, 2026

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

版本26.415.40636 (1799)

What subscription do you have?

plus

What platform is your computer?

mac m1 pro 系统: Darwin 23.4.0 arm64 arm

What issue are you seeing?

安装好 computer use ,就弹窗这个，，重新启动codex后还是会弹这个

Image

What steps can reproduce the bug?

安装好 computer use ,就弹窗报错，重启codex后,,也会弹出这个

What is the expected behavior?

No response

Additional information

No response

Activity

  1. tangxiaonian
    added
    appIssues related to the Codex desktop app
    on Apr 19, 2026
  2. github-actions
    added
    bugSomething isn't working
    tool-callsIssues related to tool calling
    on Apr 19, 2026

  3. github-actions commented on Apr 19, 2026

    @github-actions
    github-actionsbot
    on Apr 19, 2026 – with GitHub Actions
    Contributor

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

    Powered by Codex Action

  4. etraut-openai
    changed the title [-]SkyComputerUseClient 意外退出[/-] [+]SkyComputerUseClient unexpectedly exited[/+] on Apr 19, 2026

  5. qulery commented on Apr 22, 2026

    @qulery
    qulery
    on Apr 22, 2026

    After the error, this directly affects the correctness of how the context works.
    The agent is clearly forgetting part of the information that was discussed earlier and is ignoring requests.

  6. bozliu commented on Apr 22, 2026

    @bozliu
    bozliu
    on Apr 22, 2026

    I hit the same SkyComputerUseClient unexpectedly exited symptom on a different macOS setup, and I did some deeper local debugging that may help narrow the failing path.

    Environment

    • Codex app: 26.417.41555 (1858)
    • macOS: 26.4.1 (25E253)
    • Hardware: Mac15,6 / Apple Silicon
    • CODEX_HOME: /Users/bozliu/.codex (does not contain @, so this does not look like the #18555 path-parsing case)

    What was happening locally

    Before I restarted Codex, repeated crash reports were being generated for:

    • SkyComputerUseClient
    • parent process: codex-acp
    • path shape:
      /Users/bozliu/.codex/plugins/cache/openai-bundled/computer-use/1.0.755/Codex Computer Use.app/Contents/SharedSupport/SkyComputerUseClient.app/Contents/MacOS/SkyComputerUseClient

    The diagnostic reports were consistently:

    • EXC_CRASH (SIGKILL (Code Signature Invalid))
    • same repeated symptom from ~/Library/Logs/DiagnosticReports/SkyComputerUseClient-*.ips

    Recent local timestamps before the fix attempt were:

    • 2026-04-22 20:57:43 +0800
    • 2026-04-22 21:02:21 +0800
    • 2026-04-22 21:02:47 +0800
    • 2026-04-22 21:05:56 +0800
    • 2026-04-22 21:08:41 +0800

    What I verified locally

    These all succeeded locally:

    • codesign --verify --verbose=4 /Applications/Codex.app
    • spctl --assess --type execute --verbose=4 /Applications/Codex.app
    • codesign --verify --deep --strict --verbose=4 on both:
      • the app-bundled helper under /Applications/Codex.app/.../computer-use/.../SkyComputerUseClient.app
      • the cached helper under ~/.codex/plugins/cache/openai-bundled/computer-use/1.0.755/.../SkyComputerUseClient.app
    • direct CLI execution of:
      • SkyComputerUseClient --help
      • SkyComputerUseClient turn-ended '{}'
      • SkyComputerUseClient turn-ended --previous-notify '["node","/opt/homebrew/lib/node_modules/oh-my-codex/dist/scripts/notify-hook.js"]' '{}'
    • open '/Applications/Codex.app/Contents/Resources/plugins/openai-bundled/plugins/computer-use/Codex Computer Use.app'
      • this successfully launched SkyComputerUseService

    So in my case, the helper binary and even the turn-ended subcommand were not universally broken when launched directly from a normal shell parent process.

    The most useful thing I found

    Before restart, ~/.codex/config.toml had a notify = [...] entry pointing to the cached helper path under:

    • /Users/bozliu/.codex/plugins/cache/openai-bundled/computer-use/1.0.755/.../SkyComputerUseClient

    After a full Codex restart, the app rewrote notify at:

    • 2026-04-22 21:20:50 +0800

    and changed it to the app-bundled helper path under:

    • /Applications/Codex.app/Contents/Resources/plugins/openai-bundled/plugins/computer-use/.../SkyComputerUseClient

    After that restart, I observed through:

    • 2026-04-22 21:23:02 +0800

    and no new SkyComputerUseClient-*.ips files were created. The newest crash report remained the pre-restart one from 2026-04-22-210841.ips.

    Why this might matter

    This makes me suspect the failing path here was not just “Computer Use exists => crash”, but something narrower such as:

    • Codex desktop launching the cached helper path via codex-acp
    • vs launching / managing the bundled helper path inside /Applications/Codex.app

    In other words, the crash may be tied to the desktop app’s specific launch path / parent-process constraints for the cached helper, rather than the helper binary or turn-ended subcommand being generically unusable.

    Question for maintainers

    Should the desktop app ever be writing notify to a cached helper path under ~/.codex/plugins/cache/..., or should it always use the bundled helper under /Applications/Codex.app/... once installed?

    If useful, I can add the exact crash report metadata and codesign output, but I wanted to first post the path distinction because that was the strongest signal I found.

  7. qizhanchan commented on Apr 23, 2026

    @qizhanchan
    qizhanchan
    on Apr 23, 2026

    One attempt: updating to the latest macOS version resolved the error.

  8. bozliu commented on Apr 23, 2026

    @bozliu
    bozliu
    on Apr 23, 2026

    @qizhanchan Thanks for sharing that.

    In my case, this happened on April 22, 2026, with repeated crashes between roughly 20:57 and 21:08 (+0800).

    My Codex for Mac was already on the latest version I had available at the time:

    • Codex app: 26.417.41555 (1858)
    • macOS: 26.4.1 (25E253)

    So for me, it did not look like an outdated Codex build.

    What fixed it on my machine was not a macOS update. The thing that seems to have resolved it was a full Codex restart.

    After the restart, Codex rewrote the notify helper path from the old cached helper under:

    • ~/.codex/plugins/cache/openai-bundled/computer-use/.../SkyComputerUseClient

    to the bundled helper inside the app under:

    • /Applications/Codex.app/Contents/Resources/plugins/openai-bundled/plugins/computer-use/.../SkyComputerUseClient

    After that change, the crashes stopped, and so far it has not happened again on my machine.

    So at least in my case, the issue seemed more related to the helper launch path than to simply being on an old app version.

  9. bozliu commented on Apr 23, 2026

    @bozliu
    bozliu
    on Apr 23, 2026

    Closing this since the issue has not recurred on my machine after the fix/restart path described above.

  10. bozliu commented on Apr 23, 2026

    @bozliu
    bozliu
    on Apr 23, 2026

    Closing from my side to stop further notifications.

  11. jasonhemann commented on Apr 27, 2026

    @jasonhemann
    jasonhemann
    on Apr 27, 2026

    One attempt: updating to the latest macOS version resolved the error.

    Regardless, one should not need to change ones operating system in order for this software to work. That's at best a mitigation.

  12. liuhao1024 commented on Apr 29, 2026

    @liuhao1024
    liuhao1024
    on Apr 29, 2026

    I am seeing the same SkyComputerUseClient unexpectedly exited issue with a code signing crash on macOS.

    Environment:

    • Codex.app: 26.422.71525 (CFBundleVersion=2210)
    • Computer Use plugin: 1.0.758
    • macOS: 26.4.1 (25E253)
    • Mac: Mac15,8 / Apple M3 Max
    • Plugin bundle path: ~/.codex/plugins/cache/openai-bundled/computer-use/1.0.758/Codex Computer Use.app
    • Failing helper bundle ID: com.openai.sky.CUAService.cli
    • Failing helper name: SkyComputerUseClient

    Crash signature from the .ips report:

    Exception Type: EXC_CRASH (SIGKILL (Code Signature Invalid))
bundleID: com.openai.sky.CUAService.cli
procName: SkyComputerUseClient
codeSigningTeamID: 2DC432GLL2
bug_type: 309

    Local signature/Gatekeeper checks pass for both the main app and the bundled Computer Use plugin:

    $ codesign --verify --deep --strict --verbose=4 /Applications/Codex.app
/Applications/Codex.app: valid on disk
/Applications/Codex.app: satisfies its Designated Requirement

$ spctl --assess --type execute -vvv /Applications/Codex.app
/Applications/Codex.app: accepted
source=Notarized Developer ID
origin=Developer ID Application: OpenAI OpCo, LLC (2DC432GLL2)

$ codesign --verify --deep --strict --verbose=4 ~/.codex/plugins/cache/openai-bundled/computer-use/1.0.758/Codex\ Computer\ Use.app
.../Codex Computer Use.app: valid on disk
.../Codex Computer Use.app: satisfies its Designated Requirement

$ spctl --assess --type execute -vvv ~/.codex/plugins/cache/openai-bundled/computer-use/1.0.758/Codex\ Computer\ Use.app
.../Codex Computer Use.app: accepted
source=Notarized Developer ID
origin=Developer ID Application: OpenAI OpCo, LLC (2DC432GLL2)

    Additional symptoms observed locally:

    • 18 SkyComputerUseClient-*.ips crash reports were generated today.
    • 39 lingering SkyComputerUseClient mcp processes were present at the time of inspection.
    • Existing SkyComputerUseClient processes were launched from the plugin cache directory, with cwd under ~/.codex/plugins/cache/openai-bundled/computer-use/1.0.758.

    This looks less like the app/plugin bundle being unsigned on disk and more like a launch-constraint / helper process lifecycle issue where some helper launches are killed by macOS with Code Signature Invalid even though codesign and spctl both accept the installed bundles.

  13. rxaviers commented on Apr 29, 2026

    @rxaviers
    rxaviers
    on Apr 29, 2026

    In the meantime, for anyone facing this issue, it's possible to skip these errors by disabling the computer use plugin:

    Image
  14. etraut-openai
    added
    computer-use
    on May 3, 2026

  15. szupzj18 commented on May 6, 2026

    @szupzj18
    szupzj18
    on May 6, 2026

    In the meantime, for anyone facing this issue, it's possible to skip these errors by disabling the computer use plugin:

    Image

    this worked for me, thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbugSomething isn't workingcomputer-usetool-callsIssues related to tool calling

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions