Computer History wakes the locked display every 10 minutes (UserIsActive assertion from SkyComputerUseService)

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

Codex App 26.901.41600 (bundle com.openai.codex), Computer Use service com.openai.sky.CUAService 26.831.1000926 (build 1000926), Computer History plugin 1.0.1000926

What subscription do you have?

ChatGPT subscription (tier not stated)

What platform is your computer?

Darwin 25.6.0 arm64 arm — macOS 26.6.2 (25G83), MacBookPro18,1

What issue are you seeing?

With Computer History enabled, SkyComputerUseService declares a UserIsActive power assertion named "Codex Computer Use interaction" every 10 minutes, even while the Mac is locked and the display is off. Each assertion turns the display on at the login screen for ~30 seconds, after which loginwindow turns it off again. This repeats every 10 minutes around the clock, so a locked MacBook keeps lighting up all night.

Evidence from pmset -g log (311 occurrences over ~2 days, always ~10 minutes apart):

2026-09-12 17:04:03 +0200 Assertions   PID 18790(SkyComputerUseService) Created UserIsActive "Codex Computer Use interaction" 00:00:00  id:0x0x90000880d [System: DeclUser kDisp]
2026-09-12 17:04:03 +0200 Notification Display is turned on
2026-09-12 17:04:33 +0200 Notification Display is turned off
2026-09-12 17:14:03 +0200 Assertions   PID 18790(SkyComputerUseService) Created UserIsActive "Codex Computer Use interaction" 00:00:00  id:0x0x900008896 [System: PrevIdle DeclUser kDisp]
2026-09-12 17:14:03 +0200 Notification Display is turned on
2026-09-12 17:14:33 +0200 Notification Display is turned off
2026-09-12 17:24:03 +0200 Assertions   PID 18790(SkyComputerUseService) Created UserIsActive "Codex Computer Use interaction" 00:00:00  id:0x0x9000088de [System: DeclUser kDisp]
2026-09-12 17:24:03 +0200 Notification Display is turned on
2026-09-12 17:24:34 +0200 Notification Display is turned off

The unified log at each tick shows the service performing an accessibility inspection ([inc.software.app:TransformedUIElement] ... AccessibilitySupport.UIElementError Code=2) followed by a TCCAccessRequestIndirect — i.e. the periodic Computer History capture. The ticks start ~10 s after the app launches the service and continue for as long as the app is running, regardless of whether any Computer Use task is active. No 10-minute Computer History summaries are written for the locked periods, so the capture is evidently skipped while the session is locked — but only after the display has already been woken.

What steps can reproduce the bug?

1. Enable Computer History in Codex Settings (default observation settings).
2. Keep the Codex app running; lock the Mac (Ctrl-Cmd-Q) and let the display turn off.
3. Wait: every ~10 minutes the display switches on at the login screen for ~30 s.
4. Confirm the source with pmset -g log | grep "Codex Computer Use interaction" and pmset -g log | grep "Display is turned on" — the timestamps match to the second.

What is the expected behavior?

While CGSSessionScreenIsLocked is true (or the display is asleep), Computer History should neither declare user activity nor perform its periodic capture. A background observation feature should never turn on a locked display. At minimum, the assertion should be PreventUserIdleDisplaySleep-style (which does not wake a sleeping display) rather than UserIsActive.

Additional information

• Users cannot safely work around this from outside the app: with Locked Computer Use enabled, com.openai.sky.CUAService.AuthorizationPlugin.remote is registered as the first mechanism of the system.login.screensaver authorization rule, so stopping or suspending SkyComputerUseService hangs screen unlock (password accepted, then it spins / returns to the login screen). The fix therefore has to be in the service itself.
• Possibly related: #36776 (Computer Use locks an unlocked Mac after waking a sleeping display), #24367 (Chronicle screen-capture helper triggers high systemstatusd CPU).
• pmset -g on this machine: displaysleep 0, sleep 0 (on AC), so the display is only ever turned off by the lock screen's own idle timer, which makes the 10-minute wake very visible.

Start by tracing the periodic Computer History capture in SkyComputerUseService and reproduce the behavior with pmset -g log while the Mac is locked. Compare the service's accessibility inspection and power assertion activity with CGSSessionScreenIsLocked. Done means locked or sleeping displays are not awakened and no UserIsActive assertion is created during skipped captures.