Codex 26.609.41114 crashes and triggers “Codex Computer Use is damaged and can’t be opened” on macOS 26.5.1

Open 💬 5 comments Opened Jun 15, 2026 by GGBondBlueWhale

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

Version 26.609.41114
Build 3888
Released Jun 12, 2026

What subscription do you have?

ChatGPT Pro

What platform is your computer?

macOS Tahoe 26.5.1 (25F80)
Apple Silicon / ARM64
MacBook Pro 16-inch, Apple M5 Max, 128 GB memory
Hardware Model: Mac17,6

What issue are you seeing?

Codex quit unexpectedly while I was using the Codex desktop app. Around the same time, macOS also displayed a Gatekeeper-style warning for the Computer Use helper:

“Codex Computer Use” is damaged and can’t be opened. You should move it to the Trash. This file was downloaded on an unknown date.

This appears to be related to the Codex desktop app’s Computer Use / browser automation helper. The crash report shows that the main Codex app crashed, not just the helper.

Crash summary from macOS Problem Report:

  • Process: Codex
  • Path: /Applications/Codex.app/Contents/MacOS/Codex
  • Identifier: com.openai.codex
  • Version: 26.609.41114 (3888)
  • Code Type: ARM-64 (Native)
  • OS Version: macOS 26.5.1 (25F80)
  • Hardware Model: Mac17,6
  • Date/Time: 2026-06-15 00:44:09 -0700
  • Triggered by Thread: 0 CrBrowserMain, Dispatch Queue: com.apple.main-thread
  • Exception Type: EXC_BREAKPOINT (SIGTRAP)
  • Termination Reason: Namespace SIGNAL, Code 5, Trace/BPT trap: 5
  • Faulting frame includes:
  • Codex Framework
  • rust_png$cxxbridge1$194$Reader$has_trns_chunk
  • later frames include rust_bmp$cxxbridge1$194$Reader$metadata_loaded
  • System Integrity Protection: enabled

What steps can reproduce the bug?

I do not yet have a fully deterministic minimal reproduction, but the issue happened during normal Codex desktop usage involving Computer Use / browser automation.

Observed sequence:

  1. Open Codex desktop app on macOS.
  2. Use Codex normally with Computer Use / browser automation available.
  3. Codex unexpectedly quits.
  4. macOS shows the crash report: “Codex quit unexpectedly.”
  5. macOS also shows a warning dialog saying:
  • “Codex Computer Use” is damaged and can’t be opened.
  • “You should move it to the Trash.”
  • “This file was downloaded on an unknown date.”

What is the expected behavior?

Codex should not crash.

The bundled or installed “Codex Computer Use” helper should remain valid, properly signed/notarized, and launchable by macOS. Computer Use should either work normally or fail gracefully with a recoverable error message inside Codex, not trigger a macOS “damaged app” dialog and crash the main Codex desktop app.

Additional information

This looks related to other recent Computer Use / macOS Gatekeeper reports, but this report is for a newer Codex desktop version:

  • Codex App: 26.609.41114 (3888)
  • macOS: 26.5.1 (25F80)
  • Exception: EXC_BREAKPOINT (SIGTRAP)
  • Triggered thread: CrBrowserMain
  • Machine: Apple Silicon MacBook Pro, M5 Max, 128 GB memory

I can provide the full macOS crash report if needed.

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗