GPT-56T 861 —
MUSE-SPK 835 -0.7%
GPT-56SC 828 -5.2%
QWEN-38X 824 —
CL-OP55X 822 —
GROK-46H 822 -5%
GPT-6A 820 —
GLM-5 784 -8.4%
CL-FAB5H 743 -5.6%
KIMI-K3X 742 -8.4%
CL-OP5H 720 -5.8%
CL-OP5X 709 -18%
CL-OP46H 698 -5.9%
CL-OP47H 690 -5.9%
GEM-38FH 677 +0.1%
GEM-37FH 657 -24%
GPT-56S 622 —
CL-OP47 582 -0.7%
GPT-55H 582 —
INKL 531 —
GEM-31P 513 —
GEM-3P 499 —
CL-OP46 496 -0.2%
CL-OP48 490 —
GPT-56T 861 —
MUSE-SPK 835 -0.7%
GPT-56SC 828 -5.2%
QWEN-38X 824 —
CL-OP55X 822 —
GROK-46H 822 -5%
GPT-6A 820 —
GLM-5 784 -8.4%
CL-FAB5H 743 -5.6%
KIMI-K3X 742 -8.4%
CL-OP5H 720 -5.8%
CL-OP5X 709 -18%
CL-OP46H 698 -5.9%
CL-OP47H 690 -5.9%
GEM-38FH 677 +0.1%
GEM-37FH 657 -24%
GPT-56S 622 —
CL-OP47 582 -0.7%
GPT-55H 582 —
INKL 531 —
GEM-31P 513 —
GEM-3P 499 —
CL-OP46 496 -0.2%
CL-OP48 490 —
← Back to feed

OpenAI Brings Codex to Mobile: 4 Million Weekly Users Can Now Direct AI Coding Agents From Their Phones

OpenAI shipped Codex in the ChatGPT mobile app on May 14, framing it as the missing link for a new category of developer workflow: async collaboration with a coding agent running on a laptop, Mac mini, or managed cloud environment while the developer is away from their desk.

More than 4 million people use Codex every week. The mobile tab connects to any machine where Codex is running and loads live state: active threads, terminal output, diffs, test results, and pending approvals. A secure relay layer routes updates back to the phone without exposing the host machine directly to the public internet.

What it does

The mobile interface is designed for thread management rather than initiating new sessions from scratch, though that is also supported. From a phone, a developer can:

  • Review what Codex found or produced while they were offline
  • Approve or reject pending commands before they run
  • Change direction on an active thread without opening a laptop
  • Switch between models mid-session
  • Start new work if something comes to mind

Files, credentials, permissions, and local setup stay on the machine. Only output — screenshots, terminal logs, diffs, test results — flows back to the phone in real time.

Why it matters

The mechanics reflect a structural shift in how coding agents are being used. Codex tasks increasingly run for extended periods: investigating a bug, refactoring a module, generating a test suite. Those runs accumulate approval bottlenecks and decision points that previously required a developer to return to a workstation.

OpenAI is positioning Codex as infrastructure for continuous work rather than a session-bound tool. Keeping a developer reachable during a long-running task changes the effective throughput of a single agent thread.

The timing is competitive. Anthropic’s Claude Code has a similar remote-access capability via its web interface, and the developer tooling market is increasingly defined by which platform makes it easiest to stay connected to running agents across devices.

Availability

Codex in mobile is in preview. The secure relay syncs any signed-in ChatGPT account that has Codex enabled. OpenAI has not announced GA timing.

At 4 million weekly users, Codex is OpenAI’s fastest-growing developer product by active user count. The company is racing to extend that lead with Anthropic’s Claude Code also adding enterprise features at pace.