In mid-May 2026, OpenAI brought Codex remote access into the ChatGPT mobile app. The point is not to write code on a phone. It is to let you follow and steer Codex while it keeps working on a Mac.
Think of it as a mobile approval and monitoring surface: Codex still reads the project, runs commands, edits files, and checks test results on the computer; the phone is used to review progress, answer questions, add instructions, and approve actions.
For people who often let Codex run longer tasks, this is useful. You no longer need to sit in front of the Mac waiting for Codex to ask for approval or get stuck.
What it can do
According to OpenAI’s Codex remote connections documentation, mobile access can:
- start new threads in projects on the host, or continue existing ones;
- send follow-up instructions, answer questions, and steer active work;
- approve commands and other actions;
- review outputs, diffs, test results, terminal output, and screenshots;
- receive notifications when Codex completes a task or needs attention;
- switch between connected hosts and threads.
So the mobile app is not just a small chat box. It connects to the actual Codex work context on the host.
Requirements
First, you need Codex access in the ChatGPT account and workspace you want to use. The phone and Mac must use the same account and workspace.
Second, install the latest ChatGPT mobile app on iOS or Android. If Codex does not appear in the app, update ChatGPT first.
Third, the host currently needs to be a Mac that is awake, online, running the Codex App, and signed in to the same account and workspace. OpenAI’s documentation says mobile setup and device control currently require Codex App for macOS; setup is not available from Codex CLI or the IDE Extension.
Fourth, complete any required MFA, SSO, or passkey flow. In a ChatGPT workspace, an admin may also need to enable Remote Control access.
This makes the feature a mobile control layer for Codex App on macOS, not a generic remote desktop or a universal Codex connection for every environment.
Limits of Codex mobile remote access
The feature is convenient, but the limits matter.
First, it currently needs a macOS host. The phone connects to Codex App running on a Mac, not directly to Codex CLI, the IDE Extension, or any Linux / Windows development machine.
Second, the host must stay online. The Mac needs to remain awake, connected to the network, and running Codex App. If it sleeps, loses network access, or closes Codex, the remote session can disconnect.
Third, connection uses a QR-code setup flow. You start Set up Codex mobile on the Mac, scan the QR code with your phone, and finish setup in ChatGPT. It is not a simple “enter host address” flow.
Fourth, remote actions still go through approvals. You can approve commands and actions from the phone, but you should read what Codex is asking to do before confirming, especially for terminal commands, file edits, tests, and external access.
In short, it is for following up after you leave the computer. It is not a full development environment replacement and should not be treated as unattended remote control.
How to connect
Start from Codex App on the Mac:
- Open Codex on the Mac.
- Select
Set up Codex mobilein the sidebar. - Codex enables remote access for this host and shows a QR code.
- Scan the QR code with your phone to open the Codex mobile setup flow in ChatGPT.
- Confirm the same ChatGPT account and workspace.
- Complete any required MFA, SSO, or passkey verification.
- After setup succeeds, the Mac appears in Codex on your phone.
After connection, use Settings > Connections in Codex on the Mac to manage connected devices. You can also configure whether the computer stays awake, whether Computer Use is enabled, and whether the Chrome extension is installed.
What the phone is good for
The phone is best for approvals, course corrections, and result review.
Approvals are the obvious case: Codex asks to run a command or continue an action, and you can decide from the phone.
Course correction is just as useful. If Codex misunderstood the task, chose the wrong direction, or hit a failing test, you can send a short instruction and let it continue.
Result review is the third case. You can inspect diffs, test output, terminal logs, and screenshots without returning to the computer.
The value is not “coding on a phone”; it is turning the phone into a small control surface for engineering work that still runs on the host.
Common issues
If the host does not appear on your phone, confirm that Codex App is running on the Mac, Allow other devices to connect is enabled, and both devices use the same ChatGPT account and workspace.
If the approval request does not appear, open the ChatGPT mobile app, go to Codex, scan the QR code again, or restart setup from the host. Workspace users should also confirm that Remote Control access is enabled by an admin.
If the remote session disconnects, check whether the Mac slept, lost network access, or closed Codex App.
If authentication blocks setup, complete MFA, SSO, or passkey prompts first. In enterprise environments, workspace permissions may require admin help.
Best use cases
It fits users who run longer Codex coding tasks, want to approve commands away from the desk, manage multiple projects or threads, and already use a Mac as the main development machine.
It is less useful if you mainly use Windows or Linux, only use Codex CLI or an IDE Extension, expect the phone to be an independent development environment, or work on an unstable network.
My take
Codex mobile remote access is not about moving development to a phone. It is about making the waiting time around Codex more manageable.
Previously, long Codex tasks often stopped at approval, clarification, failing tests, or direction changes. Now those moments can be handled from the ChatGPT mobile app, while the Mac continues to do the actual engineering work.
If you already use Codex heavily on a Mac, this is worth enabling. If you only ask occasional coding questions, the value will be less obvious.