Codex desktop repeatedly crashes when using Computer Use.

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

• #26079
• #26357

Powered by Codex Action

Yes, this appears to be the same underlying crash signature as #26079: Codex Desktop 26.601.21317, triggered thread git, SIGABRT, node::OOMErrorHandler. My issue may add a reproduction clue: it occurs after invoking Computer Use, and my crash reports include browser-use-peer-authorization.node. I’m okay closing my issue as a duplicate if you want to track the core Node/V8 git-worker OOM in #26079, but I recommend noting the Computer Use/browser-use trigger there.

I’m seeing a very similar issue after updating to Codex 26.602.30954.

Environment:

• Codex version: 26.602.30954 • Released Jun 4, 2026
• macOS: Tahoe 26.5
• Hardware: Apple Silicon M4 Pro
• Frequency: popup appears roughly every 4 minutes

Error message:

“Codex Computer Use.app” is damaged and can’t be opened. You should move it to the Trash.

The popup appears repeatedly, even when I’m not manually launching Computer Use. This started after the latest Codex update.

The Computer Use app does not currently feel reliable or stable enough, probably because it has to interact with macOS Gatekeeper and the hardened security model in a very complex way.

The main OpenAI developer responsible for the Codex Computer Use app on macOS needs to be highly experienced, deeply familiar with macOS internals, and extremely careful. A system that can potentially take full control of a user’s machine must be engineered with exceptional precision. To work properly with macOS’s strong security model, the implementation needs to integrate organically with Gatekeeper, code signing, notarization, TCC permissions, and hardened runtime behavior. In short, this kind of feature requires real mastery of macOS, not just ordinary desktop app development.

Dear OpenAI Dev Team:

And please, do not ship features before they have been thoroughly tested across a wide variety of real-world environments. Releasing something prematurely and losing user trust is far more damaging than delaying a feature for a little longer. What matters most right now is reliability and confidence in the product, not the rapid addition of minor features that many users may not even need immediately. It would be much better to prioritize stability, eliminate these kinds of bugs and issues, and ensure a consistently dependable experience before expanding functionality further.

---

I hit what looks like the same family of issues with the intermittent macOS Gatekeeper dialog:

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

In my case this did not look like an actually corrupted helper bundle.

Environment / observed state:

• Apple Silicon macOS
• Codex.app version observed after the latest update: 26.602.30954
• Codex build: 3575
• Computer Use helper version: 809
• Helper bundle identifier: com.openai.sky.CUAService

Important paths observed:

• Bundled source helper:
• /Applications/Codex.app/Contents/Resources/plugins/openai-bundled/plugins/computer-use/Codex Computer Use.app

• Per-user Computer Use install target:
• ~/.codex/computer-use/Codex Computer Use.app

• Previous / timestamped local copy:
• ~/.codex/computer-use/Codex Computer Use.app 13-51-16-627.app

• Temporary bundled marketplace path:
• ~/.codex/.tmp/bundled-marketplaces/openai-bundled/plugins/computer-use/Codex Computer Use.app

• Runtime code-sign clone paths:
• /private/var/folders/.../X/com.openai.codex.code_sign_clone/code_sign_clone.*/Codex.app.bundle/.../Codex Computer Use.app

What I verified:

• The bundled source helper inside /Applications/Codex.app/.../computer-use/ passed:

• codesign --verify --deep --strict
• spctl --assess --type execute
• The local timestamped helper copy also passed codesign and spctl.
• The helper binaries had the same expected OpenAI Developer ID signature.
• No quarantine xattr was observed.
• SkyComputerUseService hashes matched between the bundled source and the local copy.

The local state mismatch I found:

~/.codex/config.toml had a notify hook pointing to the canonical path:

~/.codex/computer-use/Codex Computer Use.app/Contents/SharedSupport/SkyComputerUseClient.app/Contents/MacOS/SkyComputerUseClient

But at that point the canonical ~/.codex/computer-use/Codex Computer Use.app did not exist. Only a timestamped copy existed:

~/.codex/computer-use/Codex Computer Use.app 13-51-16-627.app

As a temporary test, I created a symlink from the canonical path to the timestamped copy. That made the expected path valid, and codesign / spctl still passed.

After restarting Codex and going to Settings > Computer Use > Install, Codex replaced the symlink with a real app bundle directory at:

~/.codex/computer-use/Codex Computer Use.app

The timestamped copy remained. The new canonical bundle passed codesign and spctl, and the notify target under the canonical path existed.

After that, Computer Use worked successfully against Zed.app:

• SkyComputerUseService was running.
• SkyComputerUseClient was running.
• get_app_state(app="Zed") succeeded.
• The accessibility tree and screenshot were returned.
• A click on Zed's File menu succeeded.

My interpretation:

This looks less like a bad download or broken notarization ticket, and more like a per-user Computer Use install-state / helper lifecycle / Gatekeeper interaction issue.

The issue may become visible intermittently because the relevant helper is not always launched at Codex startup. It may happen later when:

• opening Settings > Computer Use
• pressing Install
• launching the per-user helper
• launching a nested helper such as SkyComputerUseClient.app
• running the turn-ended notify hook
• attaching to the first target app
• performing the first screenshot / accessibility operation
• validating a code_sign_clone runtime copy
• TCC / Screen Recording / Accessibility checks happen

The most useful thing for maintainers may be to clarify and harden the expected lifecycle:

1. Treat ~/.codex/computer-use/Codex Computer Use.app as the canonical per-user install target, or document the intended target.
2. Ensure Codex startup and plugin refresh resync this target from the bundled app if it is missing or stale.
3. Avoid leaving config.toml notify hooks pointing to a missing canonical helper path.
4. Validate parent and nested helper apps consistently.
5. Clean up stale SkyComputerUseService, SkyComputerUseClient, node_repl, and stdio app-server helper processes after use.
6. Clean up inactive /private/var/folders/.../com.openai.codex.code_sign_clone/code_sign_clone.* directories after quit.
7. Avoid triggering repeated syspolicyd / trustd validation loops for helpers that are already signed and notarized.

This may explain why a reinstall alone did not help, but rerunning the Computer Use installer after the canonical per-user path was missing appeared to stabilize the system.

is this fixed?

Did not cash on me today. So maybe?

On Mon, Jun 8, 2026 at 2:27 PM Isaac Cohan @.***> wrote:

cohaaan left a comment (openai/codex#26458) <https://github.com/openai/codex/issues/26458#issuecomment-4652651404> is this fixed? — Reply to this email directly, view it on GitHub <https://github.com/openai/codex/issues/26458?email_source=notifications&email_token=BTZQSOOQW7QCZDVRZ7UIWAL464HSFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRVGI3DKMJUGA2KM4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4652651404>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BTZQSOIA4PRBCRS3NAPC3MD464HSFAVCNFSM6AAAAACZ2477MGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DMNJSGY2TCNBQGQ> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/BTZQSOMUUDAT4R2UP5IQRFT464HSFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRVGI3DKMJUGA2KM4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/BTZQSONKNSHMR662AG6HPYD464HSFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRVGI3DKMJUGA2KM4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you commented.Message ID: @.***>

It’s crashing all day I needed to use in cli

On Mon, Jun 8, 2026 at 4:00 PM Jeanne Duke @.***> wrote:

Cloisterwood left a comment (openai/codex#26458) <https://github.com/openai/codex/issues/26458#issuecomment-4652947032> Did not cash on me today. So maybe? On Mon, Jun 8, 2026 at 2:27 PM Isaac Cohan @.***> wrote: > cohaaan left a comment (openai/codex#26458) > <https://github.com/openai/codex/issues/26458#issuecomment-4652651404> > > is this fixed? > > — > Reply to this email directly, view it on GitHub > < https://github.com/openai/codex/issues/26458?email_source=notifications&email_token=BTZQSOOQW7QCZDVRZ7UIWAL464HSFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRVGI3DKMJUGA2KM4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4652651404>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/BTZQSOIA4PRBCRS3NAPC3MD464HSFAVCNFSM6AAAAACZ2477MGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DMNJSGY2TCNBQGQ> > . > Triage notifications, keep track of coding agent tasks and review pull > requests on the go with GitHub Mobile for iOS > < https://github.com/notifications/mobile/ios/BTZQSOMUUDAT4R2UP5IQRFT464HSFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRVGI3DKMJUGA2KM4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJKTGN5XXIZLSL5UW64Y> > and Android > < https://github.com/notifications/mobile/android/BTZQSONKNSHMR662AG6HPYD464HSFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRVGI3DKMJUGA2KM4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. > Download it today! > You are receiving this because you commented.Message ID: > @.> > — Reply to this email directly, view it on GitHub <https://github.com/openai/codex/issues/26458?email_source=notifications&email_token=BACOSGE343KP45LRX77M3K3464LM5A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRVGI4TINZQGMZKM4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4652947032>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BACOSGEVEGJRZNWQ4SLC6ML464LM5AVCNFSM6AAAAACZ2477MGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DMNJSHE2DOMBTGI> . You are receiving this because you commented.Message ID: @.>

workaround: sudo xattr ~/.codex/computer-use/Codex\ Computer\ Use.app

same issue

<img width="847" height="723" alt="Image" src="https://github.com/user-attachments/assets/ddf2d52f-4c68-4da9-8806-bbd7483da050" />

<img width="979" height="730" alt="Image" src="https://github.com/user-attachments/assets/027659f4-fd83-47d7-bc3d-e5ef707ba083" />

it happens again...