Locked use fails for manual Computer Use turn started from trusted phone/SSH connection

Summary

Locked use fails to temporarily unlock a dedicated Mac mini for a manual Computer Use turn started from the ChatGPT phone app through an existing trusted ChatGPT Connections/SSH remote project.

This is not a scheduled task. The remote turn starts successfully and can execute commands on the Mac, but the first Computer Use request fails with:

The Mac is locked and automatic unlock could not unlock it. Ask the user to unlock the Mac manually before continuing.

Expected behavior

A manual Computer Use turn started from a trusted connected device should temporarily unlock the Mac through Locked use, operate the approved app, and preserve the locked-screen protections.

Actual behavior

The remote turn reaches the Mac and runs normally until Computer Use accesses a desktop app. Automatic unlock then fails immediately and requires a manual unlock.

Reproduction

1. On a dedicated Apple-silicon Mac mini, enable Computer Use, Locked use, and "keep remote control awake while plugged in."
2. Keep the Mac powered, awake, and logged into the user session, then allow the screen to idle-lock.
3. From the ChatGPT phone app, open the existing trusted remote project connected to the Mini through ChatGPT Connections/SSH.
4. Send a manual prompt in an existing thread that requires Computer Use to inspect an approved macOS app.
5. Observe the automatic-unlock failure above.

No local keyboard, pointer, or trackpad input occurs during the attempt.

Environment

• Mac mini, Apple silicon (arm64)
• macOS 26.5.2 (25F84)
• ChatGPT/Codex desktop app 26.707.41301 (5103)
• Computer Use / authorization plug-in 26.708.1000366

Local diagnostics

• Computer Use authorization installer reports OK: installed.
• /Library/Security/SecurityAgentPlugins/CodexComputerUseAuthorizationPlugin.bundle is present.
• Installed authorization plug-in version matches the active Computer Use payload.
• Plug-in and service are signed by Team ID 2DC432GLL2.
• Authorization right com.openai.sky.CUAService.AuthorizationPlugin.remote exists and evaluates CodexComputerUseAuthorizationPlugin:allow.
• SkyComputerUseService and CUALockScreenGuardian are running.
• The Mac is on AC power; system sleep is disabled.
• keepRemoteControlAwakeWhilePluggedIn = true.
• The same phone-started turn successfully executes commands on the Mini, confirming that the trusted remote project itself is reachable.
• Around the failure window, the desktop log reports refresh_remote_control_completed ... nextConnectionCount=0, despite the phone-started remote turn continuing to execute on the host.

Suspected area

This appears consistent with the trusted remote connection context not being propagated to, or recognized by, the Computer Use Locked-use authorization handshake. The connection is sufficient to run the turn on the host, but the unlock subsystem does not recognize the Computer Use request as an eligible active trusted turn.

Please let me know which additional diagnostic logs would be useful.