Codex in the ChatGPT Mobile App: Run, Review, and Steer Codex from Your Phone
Yes, you can drive Codex from your phone. The ChatGPT mobile app on iOS and Android connects to a host running the ChatGPT desktop app on macOS or Windows, and from the phone you start work, review diffs and terminal output, and approve actions. Codex still executes on the host, which must stay awake and online.
OpenAI shipped a preview of Codex inside the ChatGPT mobile app on May 14, 2026. From your phone you start new work, review outputs, steer execution, and approve next steps -- but Codex itself keeps running on a host machine that pushes live context to mobile. Two months on, the feature has grown past its launch shape, so start with the current state below.
Update: What Changed Since the May 14 Preview
Three things in OpenAI's own documentation have moved since this article first published, and all three change the practical answer to "can I run Codex from my phone."
- Windows hosts now work. The ChatGPT what's-new entry for May 25-29, 2026 states: "Remote connections also support Windows. In the ChatGPT mobile app, open Remote to start work on a Windows device." OpenAI's remote-connections documentation now reads "Remote supports hosts running the ChatGPT desktop app on macOS and Windows." At preview launch macOS was the only host.
- There is no separate Codex app to open anymore. Per the ChatGPT what's-new log for July 6-10, 2026: "On July 9, the Codex app merged into the ChatGPT desktop app for macOS and Windows." Setup now starts in the ChatGPT desktop app, not a standalone Codex app.
- The feature is surfaced as "Remote." In the ChatGPT mobile app you open Remote to reach work running on a connected host. The launch-era phrasing "Codex remote access from ChatGPT mobile" describes the same capability.
The rest of this article covers both the current setup path and what shipped on May 14 as the historical record.
For where this fits in the Codex stack, the 0.130.0 remote-control headless app-server is the underlying plumbing for headless operation, and the April Mac computer use, browser comment mode, and thread automations post is where the "Codex for almost everything" framing started.
Key Takeaways
- Yes, you can drive Codex from a phone. iOS and Android both work, through the regular ChatGPT app -- there is no separate Codex mobile app to install.
- Hosts: macOS or Windows. Both run the ChatGPT desktop app. Windows support landed in late May 2026, after this article's original publication.
- The phone is a control surface, not a runtime. Codex keeps executing on the host; the phone loads live context from it.
- Live context surfaced to mobile. Review outputs, diffs, test results, terminal output, and screenshots; approve commands and other actions.
- The host must stay awake, online, and signed in to the same ChatGPT account and workspace. If the laptop sleeps in your bag, mobile loses live context.
- Setup starts on the host. Select "Set up Remote" in the ChatGPT desktop app sidebar, then scan the QR code with your phone.
- Availability varies by rollout, and your ChatGPT account and workspace need Codex access.
Can You Run Codex on Your Phone?
Yes, with one caveat that decides whether it fits your workflow: the phone controls Codex, it does not run it. You open Remote in the ChatGPT app on iOS or Android, and it connects to a host machine -- a Mac or Windows PC running the ChatGPT desktop app -- where Codex actually executes. From the phone you review outputs, diffs, test results, terminal output, and screenshots, and approve commands and other actions. There is no separate Codex app to download on either platform, and no way to run agent tasks locally on the handset. If the host is asleep or offline, the phone has nothing to talk to.
What "Codex in ChatGPT Mobile" Actually Is
The OpenAI Developer Community post is precise: "Now in preview: Codex in the ChatGPT mobile app". The first paragraph spells out the model:
Start new work, review outputs, steer execution, and approve next steps, all from the ChatGPT mobile app. Codex will keep running on your laptop, Mac mini, or devbox.
This is remote control of a host, not Codex running on the phone. The mobile app is a thin control layer that pulls state from wherever Codex is actually executing. The Help Center release-notes entry for May 14, 2026 names it "Codex remote access from ChatGPT mobile" and lists exactly what the mobile app loads: project context, approvals, plugins, screenshots, terminal output, diffs, and test results.
If you have been running Codex with long-horizon /goal workflows, browser comment mode, or computer-use sessions on a desktop host, this is the missing surface that lets you keep those running while you are away from the desk.
Rollout: Platforms and Availability, Then and Now
| Dimension | At preview launch (May 14, 2026) | Current (July 2026) |
|---|---|---|
| Mobile platforms | iOS and Android | iOS and Android, via the ChatGPT app |
| Host OS | macOS only; Windows coming soon | macOS or Windows |
| Host app | Standalone Codex app | ChatGPT desktop app (Codex merged in July 9) |
| Plans | All ChatGPT plans, including Free and Go | Requires Codex access in your account and workspace |
| Availability | Supported regions, rolling out gradually | "Availability can vary by rollout" |
The Windows host gap was the single biggest limitation at launch and it closed roughly two weeks later. The more recent change is structural: as of July 9, 2026 there is no separate Codex desktop app to install, so any older walkthrough that tells you to "open the Codex app" is describing a shape that no longer exists.
Setup: Pair Your Phone to a Mac or Windows Host
Per OpenAI's remote-connections documentation, you need Codex access in the ChatGPT account and workspace you want to use, the latest ChatGPT mobile app on an iOS or Android device, and the latest ChatGPT desktop app for macOS or Windows running on a host that is "awake, online, and signed in to the same account and workspace."
- Open the ChatGPT desktop app on the host and select Set up Remote in the sidebar.
- Scan the QR code shown by the app with your phone.
- ChatGPT opens the Remote setup flow. Confirm the same account and workspace, then complete any required multi-factor authentication, SSO, or passkey steps.
- Leave the host awake, online, and signed in while you use mobile.
One re-pairing rule the doc has since added: existing connections used since June 8, 2026 remain paired, but if you have not used a connection since that date, update both apps and pair the devices again. The doc also now says you can control a host from another Mac or Windows device when "Control other devices" is available, so Remote is no longer strictly phone-to-desktop.
That last requirement is load-bearing. The mobile app is not running Codex; it is reading from the host. If the laptop sleeps in your bag, the phone loses live context. For "leave it running while I commute" workflows, this implies either keeping the lid open, configuring the machine not to sleep on power, or using a Mac mini or devbox you can leave running.
One security note from the same documentation: OpenAI's expectations for the SSH host are trusted keys, least-privilege accounts, and no unauthenticated public listeners, and it advises against exposing app-server transports directly on a shared or public network. To reach a machine outside your current network, use a VPN or a mesh networking tool rather than putting the app server on the open internet.
The weekly AI Catchup
Get the week's AI coding news, distilled.
One email each week: the tools, releases, and workflows that matter for Claude Code, Codex, Cursor, and the agent stack.
How a Reader Uses This
A few concrete workflows where the mobile surface adds something real, not just a redundant UI:
- Long-running goal-mode tasks. You kicked off a multi-step
/goalworkflow in Codex CLI before lunch. From your phone, you can see when the agent hits an approval gate, scan the diff, approve, and let it keep going -- without opening a laptop. - Computer-use sessions on a Mac mini. You have Codex driving apps on a Mac mini at home or in the office. The phone lets you check what it's doing, intercept a wrong turn, and steer the next step.
- Plugin-heavy workflows. Plugins (Chrome, integrations) surface to mobile as live context. If a plugin asks for approval mid-run, you handle it on the phone.
- Test-result watch. Codex finished a test run while you were in a meeting. Mobile shows the test results and any diffs, with the same approval surface you'd see on the host.
Where mobile is the wrong surface today: long composer-style sessions where you'd be typing significant prompts, or anything where you need full IDE context. Those still belong on the host.
What This Is Not
Three clarifications to head off confusion:
- Not Codex running on the phone. The phone does not execute agent tasks locally. The host does.
- Not a replacement for the CLI or IDE. The mobile app is a control surface layered on top of the existing Codex install.
- Not a separate app download. There is no standalone "Codex mobile" app in the App Store or Play Store. The control surface is the regular ChatGPT app, under Remote.
How It Fits With Other Recent Codex Surfaces
OpenAI has shipped several Codex surfaces in close succession:
- April 16, 2026: Mac computer use, in-app browser comment mode, and thread automations -- the "Codex for almost everything" reposition.
- May 7, 2026: Codex CLI 0.129.0 shipped a
/hooksbrowser, plugin management changes, and modal Vim editing in the composer. - May 9, 2026: Codex CLI 0.130.0 added the
codex remote-controlheadless entrypoint. - May 14, 2026 (this post): Codex in the ChatGPT mobile app, preview. macOS host only.
- May 25-29, 2026: Remote connections add Windows host support.
- June 15-19, 2026: Chat handoff moves a chat and its Git state between a local computer and a connected remote host; workspace browsing and diff controls arrive on iOS.
- July 9, 2026: The Codex app merges into the ChatGPT desktop app for macOS and Windows.
The progression is consistent: Codex on more surfaces, with more ways to drive the same underlying agent from wherever you are, and steadily fewer separate apps to install. Mobile was the obvious missing surface; two months later it is a normal part of ChatGPT rather than a bolt-on.
When to Use Codex Mobile vs. the Other Surfaces
| Surface | Best for |
|---|---|
| Codex CLI | Heavy composer-style work, repo-scoped tasks, scripting via codex exec |
| ChatGPT desktop app (macOS/Windows) | Local UI, computer use, in-app browser, plugins -- the Codex app merged into this on July 9, 2026 |
| ChatGPT web app | Casual prompts, mobile-browser fallback when Remote is not available to you yet |
codex remote-control (0.130) | Running Codex headless as a service or for custom integrations |
| ChatGPT mobile, Remote (this) | Steering existing host sessions: approvals, diffs, test results, light prompts |
Caveats and Open Questions
- Still rolling out. OpenAI's documentation says "availability can vary by rollout," and access is gated on Codex being available in your ChatGPT account and workspace. If Remote does not appear in your mobile app yet, that is expected.
- Behavior keeps moving. Host requirements, the app it lives in, and the surrounding UI have all changed at least once since launch. Treat any walkthrough older than a few weeks -- including the launch-era parts of this page -- as a historical snapshot rather than current instructions.
- Privacy and audit posture. The mobile app surfaces live context including terminal output and screenshots from the host, and remote connections run over SSH to the host's app server. Teams with stricter audit requirements should treat the mobile pairing the same as adding any other remote-access path to a developer workstation, and should heed OpenAI's advice to use a VPN or mesh network rather than exposing the app server publicly.
FAQ
See structured FAQ in the schema header for question-level details: what shipped, platforms and plans, setup, what it actually is, and how it relates to other Codex surfaces.
Sources
- OpenAI Developer Community announcement: https://community.openai.com/t/now-in-preview-codex-in-the-chatgpt-mobile-app/1380940
- OpenAI Help Center, ChatGPT release notes (May 14, 2026 entry): https://help.openai.com/en/articles/6825453-chatgpt-release-notes
- ChatGPT Learn, Remote connections (host platforms, setup steps, requirements, SSH guidance): https://learn.chatgpt.com/docs/remote-connections
- ChatGPT Learn, what's new (May 25-29 Windows host entry; July 6-10 Codex app merge entry): https://learn.chatgpt.com/docs/whats-new
Read next
Keep building the workspace playbookCodex CLI 0.130.0 Adds `remote-control`, Richer Plugin Sharing Metadata, and Better App-Server Thread Paging
OpenAI shipped Codex CLI 0.130.0 in May 2026. The release adds a new `codex remote-control` command for starting a headless, remotely controllable app-server, improves app-server clients with paging options for large threads (unloaded/summary/full turn items), expands plugin sharing with link metadata and discoverability controls, adds Bedrock auth support for AWS console-login credentials from `aws login` profiles, and fixes several app-server/thread reliability issues.
OpenAI Codex Goes 'For Almost Everything': Mac Computer Use, Browser Comment Mode, and Thread Automations Explained
OpenAI shipped a major Codex update on April 16, 2026 that pushes the product past coding into general work. Three changes matter: Codex can now drive your Mac apps directly, an in-app browser captures both screenshots and DOM elements through 'comment mode', and Codex threads can run continuously to watch Slack, email, and PRs. Here is how each works, the workflows that justify each one, and where Codex now sits relative to Perplexity Personal Computer and Claude Code Routines.
Codex CLI vs Claude Code vs Cursor: 2026 Architecture Deep-Dive (Sandboxing, Context, Plugins, Scheduling)
Codex CLI, Claude Code, and Cursor all reach for the same outcome -- an AI agent that ships code -- with three different architectures. Codex enforces safety at the OS kernel layer. Claude Code uses application-layer hooks for programmable governance. Cursor builds the agent into a visual IDE with a marketplace of plugins. The right one depends less on which model you prefer and more on which architecture matches your security posture, your composition needs, and your team shape.
Frequently Asked Questions
What did OpenAI ship on May 14, 2026?
A preview of Codex inside the ChatGPT mobile app. From your phone you can start new work, review outputs, steer execution, and approve next steps. Codex itself keeps running on a host machine (laptop, Mac mini, or devbox), and the mobile app loads live context from that host: project context, approvals, plugins, screenshots, terminal output, diffs, and test results.
Can you run Codex on Android, or only iPhone?
Both. OpenAI's remote-connections documentation states you can control a host from ChatGPT on iOS or Android. There is no separate Codex mobile app to install -- the control surface is the regular ChatGPT app. Availability still varies by rollout, and your ChatGPT account and workspace need Codex access.
Does it work with a Windows host, or only a Mac?
Both, since late May 2026. OpenAI's documentation now states that Remote supports hosts running the ChatGPT desktop app on macOS and Windows. At the May 14 preview launch macOS was the only supported host and Windows was listed as coming soon; the ChatGPT what's-new entry for May 25-29, 2026 records Windows host support shipping.
How do you set it up?
Install the latest ChatGPT desktop app on the host (macOS or Windows) and the latest ChatGPT mobile app on your phone. On the host, select Set up Remote in the sidebar, then scan the QR code with your phone and confirm the same ChatGPT account and workspace. The host must stay awake, online, and signed in -- if it sleeps, the phone loses live context.
Is this Codex moving to the phone, or remote control of a host?
Remote control of a host. Codex continues running on the host (laptop, Mac mini, or devbox) and the mobile app is a control surface that loads live context from there. That is why the host has to stay awake and online. Practically, it means you can leave a long-running task at your desk and steer it on the train, but the work happens where Codex is installed.
Why does this matter relative to existing Codex surfaces?
Until now, the ways to drive Codex outside the CLI were the web app, IDE integrations, the in-app browser, and (per 0.130.0) the new `codex remote-control` headless app-server. The ChatGPT mobile surface adds a first-party, phone-native control layer that brings approvals, diffs, and terminal output to a device most people already carry. For long-running goal-mode and computer-use sessions, that is meaningfully different from refreshing the web app on a phone browser.
What can you actually do from the phone today?
Per OpenAI's announcement: start new work, review outputs, steer execution, and approve next steps. The Help Center detail lists the live context the mobile app pulls from the host -- project context, approvals, plugins, screenshots, terminal output, diffs, and test results. Treat it as the approval-and-steering surface; the host is still where heavy execution happens.