Codex Mobile cannot use Mac remote connection when host Mac is locked despite Keep this Mac awake

Resolved 💬 1 comment Opened May 21, 2026 by yorkartur Closed May 21, 2026

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

Codex App 26.519.22136 (from running app process; About dialog not rechecked)

What subscription do you have?

ChatGPT Pro/paid Codex access (please confirm exact plan before submit)

What platform is your computer?

Darwin 23.6.0 x86_64 i386macOS 14.6.1 (23G93), MacBook Pro (MacBookPro16,1, Intel Core i7)

What issue are you seeing?

Codex Mobile remote control becomes unavailable after the host Mac is locked, even though the Mac is plugged in, Codex Desktop is open, and the new remote/awake feature appears to be enabled.

Observed from iPhone 15 Pro using ChatGPT/Codex Mobile:

  • The Mac appears connected initially.
  • After the Mac is locked / display turns off, Mobile can no longer use the Mac remote connection.
  • This looks like the host becomes disconnected or unusable from Mobile while the desktop app itself is still expected to keep the machine awake.

There is no code-level error message available yet from the mobile UI; the visible user-facing symptom is that the Mac remote connection cannot be used once the Mac is in the locked state.

What steps can reproduce the bug?

  1. On macOS, open Codex Desktop and sign in.
  2. In Codex Desktop > Settings > Connections, enable remote access / Allow other devices to connect.
  3. Enable the new option intended to keep the Mac awake for remote/mobile use.
  4. Pair Codex Mobile from an iPhone 15 Pro.
  5. Leave the MacBook Pro plugged in with Codex Desktop running.
  6. Lock the Mac / let the internal display turn off.
  7. Try to continue using the Mac from Codex Mobile.

Result: Codex Mobile cannot use the remote Mac connection after the Mac is locked.

Current host power state/settings captured while investigating:

pmset -g custom
AC Power:
 sleep                0
 displaysleep         10
 womp                 1
 tcpkeepalive         1
 networkoversleep     0

Relevant assertion:
 pid(Codex): NoIdleSleepAssertion named: "Electron"

What is the expected behavior?

Codex Mobile should remain able to connect to and control the paired host Mac while the Mac is locked/display off, as long as:

  • the Mac is plugged in,
  • Codex Desktop is running,
  • remote connections are enabled, and
  • the new "Keep this Mac awake"/remote awake option is enabled.

If locked-screen remote control is not supported, the UI should clearly explain that limitation and distinguish it from sleep/offline/disconnected states.

Additional information

Related searches showed several open remote/mobile connectivity issues, but I did not find one specific to iPhone 15 Pro + locked Mac state. Examples of similar areas:

  • Codex Mobile cannot reconnect or reset remote connections after access revoked from Mac (#23413)
  • macOS remote control stalls: host app-server responsive but remote manager stays disconnected (#23482)
  • codex mobile(iphone) isn't connected to mac app. Still waiting desktop. (#23662)
  • iOS/macOS Remote Control broken after desktop update: host online, mobile 403/offline/stale Plan state (#22773)
  • Codex Desktop (MacOS) disconnects during closed-lid/mobile hotspot use despite "Prevent sleep while running" (#21703)

This report is specifically about locked Mac / display-off usage, not closed-lid clamshell mode.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗