Computer Use locks an unlocked Mac after waking a sleeping display

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

26.727.51351 (6119)

What subscription do you have?

ChatGPT Pro

What platform is your computer?

Darwin 27.0.0 arm64 arm

What issue are you seeing?

My Mac is configured to let the display sleep without locking the user session. Before starting Computer Use, the display was asleep, but the Mac was not locked and did not require authentication.

I ran a Computer Use task that launched Firefox, opened a webpage, captured a screenshot, and quit Firefox. Afterward, CUALockScreenGuardian issued a direct macOS lock. The next time the display woke, macOS required authentication.

I did not ask Codex to lock the Mac. Computer Use changed an unlocked, display-asleep session into a password-required locked session.

What steps can reproduce the bug?

Feedback ID: 019fc882-af53-7eb1-9e80-071ff3279970

1. Configure macOS so turning off the display does not lock the session or require a password.

• "Prevent automatic sleeping on power adapter when the display is off": on
• "Require password after screen saver begins or display is turned off": never

1. Disable automatic screen saver locking and allow the display to sleep.
2. Let the display turn off.
3. Start a Codex Computer Use task in a remote session, such as: “Launch Firefox, take a screenshot of the window, and quit Firefox.”
4. Let the task complete and wait approximately one minute.
5. Wake the display.
6. Observe that the Mac is now locked and requires authentication.

The behavior reproduced without any prompt or instruction asking Computer Use to lock the Mac.

What is the expected behavior?

Computer Use should preserve the Mac’s existing lock state. If the session was unlocked before the task, it should remain unlocked after the task, even if the display was asleep.

Additional information

Relevant unified-log sequence on August 3, 2026 (PDT):

• 09:49:49: loginwindow reports kLWLockFromDisplayDim (5), Keybag was NOT locked, and kLWAskForPasswordScreenWasNotLocked.
• 09:50:50.406: CUALockScreenGuardian requests PostEvent, attributed to SkyComputerUseService.
• 09:50:50.456: loginwindow receives lock reason 8, kLWLockFromDirectLock.
• 09:50:50.530: macOS sets screenIsLocked = 1.
• 09:51:20: the display turns off afterward.

This indicates the direct lock preceded the display turning off and originated from the Computer Use components, rather than from the configured display-sleep behavior.