›_ Codex Issues
Codex Issues / #30298

macOS: Codex 26.623.31921 still has invalid signatures and restores Computer Use notify hook despite disabled feature

Open 💬 5 comments Opened Jun 26, 2026 by SatyDasKap
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Summary

Codex Desktop on macOS still appears to have a signing / Gatekeeper / Computer Use regression on 26.623.31921 / build 4452.

The main app bundle and bundled Computer Use app both fail local code-signature verification. In addition, even with Computer Use disabled in config, Codex restores the SkyComputerUseClient notify hook and relaunches SkyComputerUseService.

This looks related to #28795, #28807, #28071, and #28572, but I am filing this as a current-version report because it still reproduces after updating to build 4452.

Environment

macOS: 26.5.1 (25F80)
Darwin: 25.5.0 RELEASE_ARM64_T8132 arm64
Codex Desktop: 26.623.31921
CFBundleVersion: 4452
Install path: /Applications/Codex.app
Computer Use path: ~/.codex/computer-use/Codex Computer Use.app

Current signing checks

$ codesign --verify --deep --strict --verbose=4 /Applications/Codex.app
/Applications/Codex.app: invalid signature (code or signature have been modified)
In architecture: arm64

$ spctl --assess --type execute --verbose=4 /Applications/Codex.app
/Applications/Codex.app: internal error in Code Signing subsystem

$ codesign --verify --deep --strict --verbose=4 ~/.codex/computer-use/Codex\ Computer\ Use.app
~/.codex/computer-use/Codex Computer Use.app: invalid signature (code or signature have been modified)
In architecture: arm64

Computer Use disabled, but notify hook restored

The local config had Computer Use disabled:

[features]
computer_use = false

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

A temporary local mitigation also set notify to a no-op:

notify = ["/usr/bin/true"]

After the update / relaunch, Codex rewrote the notify hook back to SkyComputerUseClient, even though computer_use=false and the plugin remained disabled:

notify = ["~/.codex/computer-use/Codex Computer Use.app/Contents/SharedSupport/SkyComputerUseClient.app/Contents/MacOS/SkyComputerUseClient", "turn-ended", "--previous-notify", "[\"/usr/bin/true\"]"]

SkyComputerUseService was also observed running again while Computer Use was disabled.

Observed impact

  • The main Codex app bundle still fails codesign --verify.
  • The bundled Computer Use app still fails codesign --verify.
  • spctl cannot assess /Applications/Codex.app and returns internal error in Code Signing subsystem.
  • SkyComputerUseService relaunches even with Computer Use disabled.
  • code_sign_clone under /private/var/folders/.../X/com.openai.codex.code_sign_clone grew to about 1.4G after update/startup before local cleanup.
  • syspolicyd / trustd CPU only drops after disabling the CUA notify hook and stopping the helper.

Representative macOS log message:

Entitlement com.apple.security.application-groups=(
    "2DC432GLL2.com.openai.sky.CUAService"
) is ignored because of invalid application signature or incorrect provisioning profile

Expected behavior

  • /Applications/Codex.app should pass codesign --verify --deep --strict.
  • ~/.codex/computer-use/Codex Computer Use.app should pass codesign --verify --deep --strict.
  • spctl --assess --type execute /Applications/Codex.app should succeed.
  • Setting computer_use=false should prevent Computer Use helpers from launching.
  • Setting computer_use=false should prevent Codex from installing or restoring a SkyComputerUseClient notify hook.
  • Codex should not trigger repeated Gatekeeper / trustd / syspolicyd assessment loops or code_sign_clone growth.

Notes

This report intentionally uses normalized paths such as ~/.codex and /private/var/folders/... to avoid including machine-specific user paths. The failures above are from local commands on the affected macOS machine after updating to 26.623.31921 / build 4452.

View original on GitHub ↗

5 Comments

SatyDasKap · 2 months ago

Additional hardware context, with machine-specific identifiers intentionally omitted:

Model Name: MacBook Pro
Model Identifier: Mac16,1
Chip: Apple M4
CPU cores: 10 total (4 performance, 6 efficiency)
Memory: 24 GB

I am intentionally not including serial number, hardware UUID, provisioning UDID, hostname, or local user paths.

github-actions[bot] contributor · 2 months ago

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

  • #28807
  • #28795
  • #29350
  • #29157
  • #30053

Powered by Codex Action

dgobaud · 1 month ago

related / duplicate with additional info maybe - https://github.com/openai/codex/issues/31251

jayjay91 · 27 days ago

I can reproduce the Computer Use relaunch problem on a newer build.

Environment:

  • ChatGPT/Codex Desktop: 26.727.40816 (build 6067)
  • Computer Use helper: 26.727.1000550
  • macOS 26.0.1 (25A362), arm64

User-visible behavior:

  • macOS continuously displays “Record & Replay is recording your actions.”
  • Clicking “Stop Recording” does nothing.
  • Quitting and reopening ChatGPT immediately restarts the recording.

Computer Use was explicitly disabled:

toml
[features]
computer_use = false

The plugin and MCP server were also disabled/uninstalled, and Screen Recording and Accessibility permissions were revoked.

Nevertheless, on startup ChatGPT:

Changed computer-use-bundled-plugin-auto-install-disabled from true back to false.
Recreated ~/.codex/computer-use.
Re-added the SkyComputerUseClient turn-ended notify hook.
Relaunched SkyComputerUseService.

The helper passed code-signature verification and was signed by OpenAI OpCo, LLC, so this instance does not appear to involve an invalid signature.

The only effective workaround was placing an immutable filesystem sentinel at ~/.codex/computer-use, preventing ChatGPT from recreating the helper directory.

chilu18 · 27 days ago

Misleading Record & Replay recording indicator on macOS

Independent reproduction with additional status-level evidence on the current build.

Environment

  • macOS 26.0.1 (25A362), arm64
  • ChatGPT/Codex Desktop 26.727.40816 (build 6067)
  • Codex Computer Use helper 26.727.1000550 (build 1000550)

Observed behavior

  • ChatGPT automatically launched SkyComputerUseService at 14:16:49.
  • Its menu item and accessibility label said: “Record & Replay is recording your actions.”
  • The helper's own Record & Replay MCP status returned:
{
  "isRecording": false,
  "maxDurationSeconds": 1800
}
  • Calling event_stream_stop also returned isRecording: false.
  • The ReplayKit launch log reported isActive 0.
  • No events.jsonl, metadata.json, session recording, or open recording file was found.
  • A live idle check showed no continuous network traffic.
  • Sending SIGTERM to SkyComputerUseService immediately removed the menu-bar item.
  • The helper passed strict code-signature verification and Gatekeeper assessment and is signed by OpenAI OpCo, LLC.

Assessment

The status item appears to be tied to helper presence or stale UI state rather than event_stream_status. This creates a high-trust privacy indicator that says recording is active when the backend says it is not. I found no evidence that screen content was actually recorded or streamed in this reproduction.

Expected behavior

  • Do not show a recording indicator when isRecording is false.
  • The accessibility label should reflect the backend state.
  • Stop Recording should remove or refresh a stale indicator.
  • Computer Use should not auto-launch this status item when no Computer Use or Record & Replay task was initiated.

Evidence prepared

  • record-replay-item-visible.png: original menu-bar screenshot showing the indicator.
  • record-replay-item-removed.png: menu-bar-only screenshot after stopping the helper.

The screenshots exclude browser content, hostname, local paths, and credentials. GitHub attachment upload is pending because the ChatGPT Chrome extension currently does not have local-file access.

OpenAI feedback correlation

Submitted through Codex /feedback as a bug without diagnostic logs. Feedback thread ID: 019fb881-3577-7501-a443-216eacb7e9dd.