macOS: Computer History status polling wakes sleeping displays every 10 minutes

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

ChatGPT/Codex desktop app 26.901.31953 (build 7868), verified from the installed app's Info.plist.

Computer Use helper: 26.831.1000926 (build 1000926).

What subscription do you have?

Not included in the diagnostic capture.

What platform is your computer?

macOS 26.6.2 (build 25G83), Apple M4, connected to AC power.

What issue are you seeing?

The displays repeatedly turn on overnight while Computer History is enabled. The power logs show 42 display wakes between midnight and 07:00 on September 4, 2026, with all 41 intervals exactly 600 seconds. The displays remained on for 30 seconds in 41 cases and 31 seconds in one case.

Every one of those 42 display-on events immediately followed SkyComputerUseService creating a UserIsActive assertion named Codex Computer Use interaction.

A later wake was traced to a Computer History status request, providing a specific background request to investigate. This event occurred before the diagnostic investigation started, so it was not caused by the diagnostic status checks.

Sanitized macOS unified-log excerpt, September 4, 2026 (UTC-04:00):

20:35:46.617 SkyComputerUseService: ComputerUseIPCSkysightStatusRequest
20:35:46.623 SkyComputerUseService: ComputerUseIPCSkysightStatusRequest

Corresponding power-log excerpt:

20:35:46 SkyComputerUseService Created UserIsActive "Codex Computer Use interaction"
20:35:46 SkyComputerUseService Created PreventUserIdleDisplaySleep "Codex Computer Use interaction"
20:35:47 Display is turned on
20:36:17 Display is turned off

The desktop app log also records an interval-triggered feature refresh and a local app-server starting/running transition around the same time. The exact internal cause of the repeated polling/reconciliation has not been proven.

This prevents the user from keeping the screens dark at night while leaving the computer available for background work.

What steps can reproduce the bug?

Observed setup and suggested reproduction:

1. Run the desktop app and enable Computer History.
2. Leave the computer running on AC power with the displays asleep. On the affected machine, pmset -g custom reports sleep 0 and displaysleep 10.
3. Leave the app open and observe the displays and power logs for more than 10 minutes.
4. Check for SkyComputerUseService user-activity/display-sleep assertions immediately preceding each display-on event.
5. Correlate a wake with macOS unified logs for SkyComputerUseService; the captured request was ComputerUseIPCSkysightStatusRequest.

The pattern was reconstructed from an overnight log and a later wake on the affected machine. It has not been independently reproduced on another machine, and no controlled test after disabling Computer History has been completed.

What is the expected behavior?

Background Computer History status requests should not declare user activity, wake sleeping displays, or briefly prevent display sleep. The computer should be able to continue background work while its screens remain off.

Please check whether passive status/health requests pass through the same display-wake assertion wrapper as intentional interactive Computer Use actions.

Additional information

• No scheduled macOS wake events were listed by pmset -g sched.
• Computer History was confirmed running during diagnosis.
• The user plans to disable Computer History as a workaround; its effectiveness is not yet verified.
• Related: #42690 reports Computer Use assertions correlated with FullWake cycles and later GPU/display failures. This report isolates a status-request-associated, exactly 10-minute display-wake pattern; it does not assert that the separate GPU failure occurred here.
• Only the relevant sanitized event excerpts are included. No screenshots, conversation contents, personal filesystem paths, account identifiers, or full diagnostic logs are attached.

Start by tracing ComputerUseIPCSkysightStatusRequest through SkyComputerUseService and comparing its assertion path with intentional interactive Computer Use actions. Use the provided unified and power-log pattern to investigate whether passive status polling creates display-wake assertions; done means background status requests no longer wake displays or prevent display sleep.