macOS 27 Golden Gate beta: computer/browser control stops when locked, with no apparent permission request

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

26.901.51231 (build 8109), read from the installed application's Info.plist.

The installed application is named ChatGPT.app.
Bundle identifier: com.openai.codex.

What subscription do you have?

Pro x20

What platform is your computer?

• macOS 27.0 Golden Gate beta, build 26A5425a
• MacBook Pro, model identifier MacBookPro18,2
• Apple M1 Max

Output of uname -mprs:

Darwin 27.0.0 arm64 arm

Related software:

• Google Chrome: 152.0.7977.83
• ChatGPT Chrome extension: 1.26.901.11451
• Extension ID: hehggadaopoacecdllhhajmbjkdcmajg

What issue are you seeing?

Computer use stops working when the Mac screen is locked on macOS Golden Gate beta. One affected workflow is controlling Google Chrome through the ChatGPT browser extension.

I do not see a corresponding system permission prompt or a relevant entry appearing in System Settings that would let me grant the required access.

This may relate to permission changes in Golden Gate, possibly under System Settings > Privacy & Security > Automation. However, the responsible permission category and the root cause have not been confirmed.

I have also tried disabling the screen saver, automatic screen locking, and sleep, but browser control still stops working. It is not yet established whether this and the locked-screen failure have the same cause.

What steps can reproduce the bug?

1. On macOS 27.0 beta (26A5425a), open ChatGPT and connect its Chrome extension.
2. Start a task that controls Google Chrome and confirm that interaction works with the screen unlocked.
3. Lock the Mac while the task is running.
4. Observe that computer/browser control stops working.
5. After unlocking, inspect System Settings > Privacy & Security. No corresponding permission request or relevant entry appears that would let me grant access.

Disabling the screen saver, automatic locking, and sleep has not resolved the issue.

These steps describe the user's observed behavior. The diagnostic collection did not deliberately lock the Mac or reproduce the failure.

What is the expected behavior?

Browser control should remain reliable while the Mac is awake and unlocked.

If the relevant automation is supported while the screen is locked, the application should request the necessary permissions.

If macOS requires an unlocked session, the application should explain this limitation and provide a clear way to resume the task.

If a required permission is missing, the application should trigger the appropriate system permission flow or identify the exact setting that needs to be changed.

Additional information

Local diagnostics collected on September 8, 2026:

Power and sleep:

• The Mac was connected to AC power.
• AC power settings: system sleep = 0 (disabled), display sleep = 0 (disabled).
• Battery settings: system sleep = 1 minute, display sleep = 0 (disabled).
• A screen-sharing connection was active during diagnostic collection.

Chrome native messaging:

• The com.openai.codexextension.json native messaging host manifest is present.
• The executable referenced by the manifest exists.
• The installed ChatGPT extension ID is included in the manifest's allowed origins.
• These checks confirm registration files are present; they do not prove that communication remains functional while the screen is locked.

Permission verification limitations:

• The local macOS TCC database could not be opened for read-only inspection.
• Therefore, the absence of a relevant permission entry is a user observation, not independently verified by the diagnostics.
• Legacy screen saver and password-delay preference keys were absent, so the current automatic-lock settings could not be verified through those keys.
• No system settings were changed during diagnostic collection.

No exact error message or recovery behavior after unlocking was captured.

No source files, tests, or entry points are named. Start by reproducing the failure on macOS 27.0 beta with ChatGPT and the Chrome extension, then trace the permission or locked-session behavior; done means control either works as expected, or the app clearly reports the limitation and provides a reliable recovery path.