What version of the Codex App are you using (From “About Codex” dialog)?
26.513.31313 (2867)
What subscription do you have?
Plus
What platform is your computer?
Darwin 25.4.0 arm64 arm
What issue are you seeing?
Left my MacBook Pro at home connected to power and an external monitor with the Codex app running today, and the Connections → Control this Mac → Keep this Mac Awake setting enabled. Despite this, my Mac went to sleep, dropped off the network, and became unavailable in the Codex section of the ChatGPT app on my iPhone.
What steps can reproduce the bug?
- Connect your Mac to power.
- In Codex, Connections → Control this Mac → Keep this Mac Awake: ON
- Make sure both the Mac and iPhone are on the same TailScale Tailnet.
- Set up an iPhone with access to Codex on your Mac from the ChatGPT app on iOS.
- Leave the Mac idle until the display turns off (System Settings → Lock Screen → Turn display off on power adapter when inactive)
- Note that the Mac goes to sleep and becomes unavailable on the Tailnet, and in the ChatGPT app on iPhone.
What is the expected behavior?
With the option to "Keep this Mac awake" enabled, I would expect my Mac's screensaver to still turn on, for the display to sleep, but for the Mac to remain online and responsive to external connections from the ChatGPT app on mobile.
Additional information
Here are my macOS Battery options (which, despite the name, is where you configure power settings for the machine when it is connected to power in macOS Tahoe):
Here are my macOS Lock Screen options:
My Mac and iPhone are on the same Tailnet. The TailScale app showed the Mac as offline when it was asleep.
Interestingly, I also run OpenClaw on this machine, and while the computer was showing as offline in TailScale, and not responding to Codex connection attempts from the ChatGPT mobile app, it was still able to respond (with a delay of around a minute) to Telegram messages sent to my OpenClaw bot. Whenever I would send a message, it would respond only after about a minute's delay, and at the moment where it responded, my Mac would show up as online in TailScale for just a moment, while OpenClaw was responding to my message, then it dropped offline again. It seems as if OpenClaw is able to still receive requests and temporarily wake the Mac from sleep to respond to them, whereas the Codex desktop app does not.
What version of the Codex App are you using (From “About Codex” dialog)?
26.513.31313 (2867)
What subscription do you have?
Plus
What platform is your computer?
Darwin 25.4.0 arm64 arm
What issue are you seeing?
Left my MacBook Pro at home connected to power and an external monitor with the Codex app running today, and the Connections → Control this Mac → Keep this Mac Awake setting enabled. Despite this, my Mac went to sleep, dropped off the network, and became unavailable in the Codex section of the ChatGPT app on my iPhone.
What steps can reproduce the bug?
What is the expected behavior?
With the option to "Keep this Mac awake" enabled, I would expect my Mac's screensaver to still turn on, for the display to sleep, but for the Mac to remain online and responsive to external connections from the ChatGPT app on mobile.
Additional information
Here are my macOS Battery options (which, despite the name, is where you configure power settings for the machine when it is connected to power in macOS Tahoe):
Here are my macOS Lock Screen options:
My Mac and iPhone are on the same Tailnet. The TailScale app showed the Mac as offline when it was asleep.
Interestingly, I also run OpenClaw on this machine, and while the computer was showing as offline in TailScale, and not responding to Codex connection attempts from the ChatGPT mobile app, it was still able to respond (with a delay of around a minute) to Telegram messages sent to my OpenClaw bot. Whenever I would send a message, it would respond only after about a minute's delay, and at the moment where it responded, my Mac would show up as online in TailScale for just a moment, while OpenClaw was responding to my message, then it dropped offline again. It seems as if OpenClaw is able to still receive requests and temporarily wake the Mac from sleep to respond to them, whereas the Codex desktop app does not.