Locked Computer Use authorization plug-in is registered but rejected by macOS SecurityAgentHelper Library Validation

Resolved 💬 1 comment Opened May 22, 2026 by anchia-hsu Closed Jul 10, 2026

Summary
Codex Locked Computer Use is enabled in Settings, but when the Mac is locked and I continue the Codex thread from iPhone Remote Control, Computer Use fails before interacting with the target app. The visible failure in Codex is Failed: Get app state. Local investigation shows that the Codex authorization plug-in is installed and registered in macOS authorizationdb, but SecurityAgentHelper rejects it at load time with a Library Validation error.

Environment

  • macOS: 26.5 (25F71)
  • Hardware: Apple Silicon
  • Codex app: 26.519.31651 (CFBundleVersion 3017)
  • Codex Computer Use helper: build 799
  • Codex Computer Use service bundle ID: com.openai.sky.CUAService
  • Authorization plug-in bundle ID: com.openai.sky.CUAService.AuthorizationPlugin
  • Plug-in path: /Library/Security/SecurityAgentPlugins/CodexComputerUseAuthorizationPlugin.bundle

User-visible behavior

  1. Enable Codex Settings > Computer use > Locked use.
  2. Lock the Mac.
  3. Use iPhone Remote Control to continue a Codex thread and ask Codex to operate Reminders.
  4. Codex fails at Get app state before it can inspect or control the app.
  5. The same workflow can fall back to AppleScript, which suggests the app itself is controllable, but Computer Use cannot acquire app state while locked.

Local checks that pass

  • The plug-in exists at /Library/Security/SecurityAgentPlugins/CodexComputerUseAuthorizationPlugin.bundle.
  • security authorizationdb read system.login.screensaver includes:
  • com.openai.sky.CUAService.AuthorizationPlugin.remote
  • use-login-window-ui
  • security authorizationdb read com.openai.sky.CUAService.AuthorizationPlugin.remote shows:
  • class = evaluate-mechanisms
  • mechanisms = CodexComputerUseAuthorizationPlugin:allow
  • comment says it asks SkyComputerUseClient whether an active Computer Use login authorization is pending.
  • codesign --verify --deep --strict --verbose=4 /Library/Security/SecurityAgentPlugins/CodexComputerUseAuthorizationPlugin.bundle passes.
  • codesign --verify --deep --strict --verbose=4 "$HOME/.codex/computer-use/Codex Computer Use.app" passes.
  • codesign --verify --deep --strict also passes for:
  • SkyComputerUseClient.app
  • CUALockScreenGuardian.app

Key system log evidence
During a locked-use attempt, unified logs show SecurityAgentHelper trying to load the staged plug-in and rejecting it:

Library Validation failed: Rejecting '/Library/Security/SecurityAgentPlugins/StagedPlugins/CodexComputerUseAuthorizationPlugin.bundle/Contents/MacOS/CodexComputerUseAuthorizationPlugin' (Team ID: 2DC432GLL2, platform: no) for process 'SecurityAgentHelper-arm64' (Team ID: N/A, platform: yes), reason: mapping process is a platform binary, but mapped file is not

Followed by:

Error loading /Library/Security/SecurityAgentPlugins/StagedPlugins/CodexComputerUseAuthorizationPlugin.bundle/Contents/MacOS/CodexComputerUseAuthorizationPlugin (146): dlopen(... not valid for use in process: mapping process is a platform binary, but mapped file is not)

And authd still reports:

engine 182: running mechanism CodexComputerUseAuthorizationPlugin:allow (1 of 1)
Successfully removed staged plugin: /Library/Security/SecurityAgentPlugins/StagedPlugins/CodexComputerUseAuthorizationPlugin.bundle

Interpretation
macOS appears to accept the authorizationdb configuration, and the OpenAI-signed plug-in verifies on disk, but SecurityAgentHelper refuses to map the non-platform plug-in into a platform binary process. This looks like a compatibility/signing/Library Validation problem for Locked Computer Use on macOS 26.5, not a normal Accessibility or Screen Recording permission issue.

Expected behavior
When Locked Computer Use is enabled, Codex should be able to use the registered authorization plug-in to temporarily unlock for the active trusted Computer Use turn, then acquire app state and operate the approved app.

Actual behavior
The authorization plug-in is registered but rejected at load time by SecurityAgentHelper. Codex then fails with Failed: Get app state while the Mac is locked.

Could the Codex team confirm whether build 799 of CodexComputerUseAuthorizationPlugin.bundle is expected to load under macOS 26.5 SecurityAgentHelper, and whether a platform-compatible signing or entitlement change is needed?

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗