OpenAI brought Codex to ChatGPT’s mobile app on May 14, 2026 — across iOS and Android in preview, available on all tiers including Free and Go. The OpenAI Codex mobile experience lets developers review outputs, approve commands, steer threads, and manage active coding tasks from their phone, with Codex sessions running on local Macs, laptops, devboxes, or remote servers staying in sync via cloud relay. The same update added remote SSH improvements, hooks, access tokens, and HIPAA-eligible deployment for healthcare engineering teams. The shift positions Codex as a complete cloud-synced AI coding assistant rather than a desktop-only tool.
What’s actually new
Codex on mobile reframes how AI coding gets done. The previous experience was desktop-centric: open Codex CLI on your Mac or use ChatGPT’s Codex panel on your computer. Mobile users were stuck without good access. The May 14 release brings Codex into the ChatGPT mobile app — same iOS and Android app most ChatGPT users already have. No separate app, no new login. Users see their active Codex threads and can interact with them on phone the same way they would on desktop.
The architecture matters. Codex still runs on the actual development environment — your Mac, your laptop, your devbox. The mobile app is a remote control. Files, credentials, and local configurations stay on the host machine. The phone shows live updates: diffs of file changes, terminal output, test results, approval prompts. When Codex wants to run a command, you approve from the phone. When it produces a code change, you can review and decide.
This solves the real problem of being away from your computer when Codex needs input. The pattern: kick off a long-running Codex task before lunch; check progress from phone during lunch; approve a few commands while in line for coffee; come back to a fully-completed feature. The mobile experience extends Codex from a desktop-bound tool to anytime-anywhere AI pair programming.
Beyond mobile, the same release added enterprise features. Remote SSH improvements make Codex more capable on remote development environments. Hooks allow Codex to integrate with team processes. Access tokens enable secure programmatic access. HIPAA support lets healthcare engineering organizations use Codex on protected health information under data processing agreements — opening a substantial enterprise use case.
The pricing is competitive: Codex mobile is included in all ChatGPT tiers including Free and Go. There’s no separate Codex subscription required; existing ChatGPT users get the capability. Heavy Codex use may push into rate-limited territory on lower tiers, but exploration is free.
Why it matters
- OpenAI Codex becomes truly portable. The desktop-bound limitation that constrained AI coding tools loosens. Developers can stay connected to ongoing work without being at their desk.
- Mobile interaction model matures. Reviewing diffs and approving commands on a phone screen is genuinely usable. The UX establishes patterns that other AI coding tools will adapt.
- Free tier inclusion lowers adoption barriers. Free users can experience Codex mobile, expanding the developer audience significantly.
- HIPAA support unlocks healthcare engineering. Healthcare codebases were previously off-limits for many AI coding tools due to compliance concerns. Codex with HIPAA changes that.
- Pressure on Claude Code, Cursor, GitHub Copilot. Each has different mobile stories; OpenAI’s polished mobile experience raises the bar.
- Long-running AI tasks become more practical. Knowing you can monitor and approve from anywhere makes longer Codex sessions less risky to start.
How to use it today
OpenAI Codex mobile is live as of May 14, 2026. Practical setup:
- Update your ChatGPT mobile app. The Codex feature is part of the standard ChatGPT app, not a separate app.
# iOS: # App Store → Updates → ChatGPT → Update if available # Or fresh install: search "ChatGPT" by OpenAI # Android: # Play Store → ChatGPT → Update if available # Or fresh install: search "ChatGPT" by OpenAI # Open the app; sign in with your existing ChatGPT account. - Make sure Codex is set up on your development machine. Codex mobile is a remote control for Codex running elsewhere.
# On Mac/laptop/devbox, install Codex CLI if not already: # Visit https://developers.openai.com/codex # Follow current install instructions # Authenticate Codex with your OpenAI account # (same account as your ChatGPT mobile login) # Start a Codex session: codex start # This becomes accessible from your phone via cloud relay - Connect mobile to your active sessions. Open ChatGPT mobile app; navigate to Codex section.
# In the ChatGPT mobile app: # - Look for Codex tab or section in the sidebar # - Your active Codex sessions appear listed # - Tap a session to enter it # Each session shows: # - Recent activity # - Pending approvals (commands awaiting your OK) # - Diffs of file changes # - Terminal output # - Conversation history - Try a representative workflow. Test on a real but non-critical task first.
# Example mobile Codex workflow: # 1. Start a task on desktop: "refactor the user authentication # module to use the new JWT pattern" # 2. Leave desk; open ChatGPT mobile # 3. Watch Codex progress through the task # 4. When Codex proposes terminal commands, review and approve # 5. When Codex completes file edits, review the diffs # 6. Approve or request changes # 7. Return to desk; verify final state # Sub-30 minute tasks are good first tests. - Configure for your security posture. Especially for sensitive work.
# Security considerations: # Mobile access expands attack surface: # - Lost phone could expose Codex sessions # - Enable phone PIN/biometric lock # - Use ChatGPT app's session-locking if available # For corporate use: # - Check IT policy on mobile development tool access # - Consider whether some codebases shouldn't sync to mobile # For healthcare (HIPAA): # - Confirm BAA in place with OpenAI # - Use HIPAA-eligible deployment configuration # - Monitor access patterns - Set up remote SSH if developing on remote servers. The Codex update includes better remote SSH support.
# If you develop on remote servers via SSH: # Codex now handles SSH connections more capably # Configure SSH keys for Codex's machine identity # Set up appropriate firewall rules # Verify session persistence across SSH disconnects - Try hooks for team workflow integration. Hooks let Codex events trigger your team’s processes.
# Example hook patterns: # - On Codex completion, post to team Slack channel # - On Codex approval, log to audit system # - On Codex error, notify on-call engineer # Configuration varies; check Codex docs for current syntax # Hooks let Codex be a citizen of your team's broader workflows. - For HIPAA use, verify the deployment setup. Healthcare orgs need specific configuration.
# HIPAA Codex deployment checklist: [ ] BAA signed with OpenAI [ ] HIPAA-eligible workspace or organization configured [ ] Audit logging enabled [ ] Access controls per HIPAA requirements [ ] Workforce training on HIPAA-compliant use [ ] Incident response procedures cover Codex # Contact OpenAI enterprise sales for HIPAA setup specifics. - Provide feedback to OpenAI. Early users shape the mobile experience.
How it compares
Codex mobile lands in a competitive AI coding landscape. Comparison:
| Tool | Mobile experience | Cloud sync | HIPAA |
|---|---|---|---|
| OpenAI Codex (now mobile) | Full ChatGPT app integration on iOS/Android | Yes — local execution + cloud relay | Yes — HIPAA-eligible |
| Claude Code | Limited mobile; terminal-driven on desktop | Limited cloud sync | Via Anthropic Enterprise with BAA |
| GitHub Copilot | VS Code mobile features limited; primary on desktop | Via VS Code Live Share + GitHub Codespaces | Via GitHub Enterprise with BAA |
| Cursor | Desktop-focused; mobile limited | Not native; via Cursor cloud features | Via enterprise tier |
| JetBrains AI Assistant | Desktop IDE focused | Limited | Via JetBrains enterprise |
What distinguishes Codex mobile: complete mobile workflow integration, cloud sync that keeps local files local while making review/approval remote, HIPAA-eligible deployment for healthcare. The risks: relatively new mobile experience; depends on continued OpenAI investment; UX for complex review tasks on small screens is inherently limited.
What’s next
Signals to watch over the next 3 months. Adoption velocity: how many ChatGPT mobile users actually try Codex. UX iteration: mobile UX for code review will refine based on user feedback. Competitive response: Anthropic, GitHub, JetBrains likely accelerate their own mobile stories. Healthcare uptake: HIPAA support opens healthcare engineering use cases; pilots will reveal viability. Cloud relay reliability: the sync between local execution and mobile control must be consistently reliable for the experience to feel professional.
The longer-term picture. AI coding is shifting from desktop-bound to anywhere-accessible. Mobile is part of that. The future likely includes: mobile-first AI coding tools for specific workflows, persistent cloud-based coding agents that run continuously, deeper integration between AI coding and broader developer workflow tools. OpenAI Codex mobile is a step in that direction; competitors will follow.
For developers today, the practical implication: AI coding becomes less location-bound. Whether or not you adopt Codex specifically, expect mobile AI coding to be a normal capability within 12-18 months.
Frequently Asked Questions
Do I need a paid ChatGPT subscription to use Codex mobile?
No — Codex mobile is available across all ChatGPT tiers including Free and Go. Heavy use may push against rate limits on lower tiers, but baseline access is universal.
Does Codex actually run on my phone?
No. Codex executes on your Mac, laptop, devbox, or remote server. The phone is a control interface. Files and credentials stay on the host machine; the phone receives updates and sends approvals via cloud relay.
How does Codex mobile compare to using ChatGPT mobile for coding questions?
ChatGPT mobile is conversational AI for general coding questions. Codex mobile manages an active coding session with file changes, terminal commands, and ongoing work. Different use cases; complementary capabilities.
Is Codex mobile safe for production code?
The mobile experience itself is OpenAI’s same security infrastructure as ChatGPT. Files don’t sync to phone; only diffs and outputs do. Approve commands carefully. For most production work, the model is similar to using Codex on desktop — same risks; same mitigations apply.
How does HIPAA support actually work?
OpenAI offers HIPAA-eligible deployments under appropriate data processing agreements. Healthcare engineering teams can sign a BAA with OpenAI, configure their workspace as HIPAA-eligible, and use Codex on PHI-touching code. Specific terms and configuration require OpenAI enterprise contact.
Can I use Codex mobile without internet?
No. The mobile-to-host relay requires internet. Codex itself on your host machine can work offline for some tasks but the mobile control aspect needs connectivity.
What if my host machine is offline when I want to check from phone?
You can see the latest state from when the host was last connected, but can’t issue new commands until the host reconnects. The mobile experience degrades gracefully — read-only access to past state, full access when host is online.