Computer Use locks an unlocked Mac after waking a sleeping display
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start by tracing the Computer Use components named in the report, especially CUALockScreenGuardian and SkyComputerUseService, and compare their behavior with the provided unified-log sequence. Reproduce the display-sleep configuration and remote task, then verify that an unlocked session remains unlocked after the task completes.
Written by the indexing model from the issue text.
Description
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
- 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
- Disable automatic screen saver locking and allow the display to sleep.
- Let the display turn off.
- Start a Codex Computer Use task in a remote session, such as: “Launch Firefox, take a screenshot of the window, and quit Firefox.”
- Let the task complete and wait approximately one minute.
- Wake the display.
- 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:
loginwindowreportskLWLockFromDisplayDim (5),Keybag was NOT locked, andkLWAskForPasswordScreenWasNotLocked. - 09:50:50.406:
CUALockScreenGuardianrequestsPostEvent, attributed toSkyComputerUseService. - 09:50:50.456:
loginwindowreceives 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.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- Avg merge
- 1m
- Merged PRs (30d)
- 1k
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openai/codex
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug CLI windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
macOS sandbox blocks hw.optional.arm64 sysctl, causing Flutter to misdetect Apple Silicon as x64 Openbug CLI sandbox
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug CLI TUI
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
CLI config enhancement skills
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
A-linter
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oxc-project/oxc#26863 ·