OpenAI readies remote control for Codex inside the ChatGPT mobile app

OpenAI looks like it’s turning ChatGPT on your phone into a remote for Codex. Not a full mobile IDE — more like a control surface for coding agents already running elsewhere. That matters because Codex is no longer just “write me a function.” It’s becoming a long-running workspace where agents keep working after you leave the keyboard. The gap has been obvious for a while — once you step away from your desk, oversight gets clumsy. Now the mobile app seems to be the fix. ### What actually showed up? The strongest evidence is inside the ChatGPT Android app, version 1.2026.125. Reported strings point to reconnecting to a Codex session from mobile, with setup text telling users to keep Codex open on a desktop computer and signed into the same account. That suggests phone control for an already-running session, not local coding on Android itself. (testingcatalog.com) ### Why does that matter for Codex? Because Codex is built for long jobs. OpenAI’s own product pages pitch it as a command center for multi-agent software work, with separate threads, cloud environments, worktrees, and tasks that can run in parallel across projects. Once the product works that way, desktop-only control starts to feel like a bottleneck. ### So is this just a rumor? Mostly yes — but it’s a pretty grounded one. (androidauthority.com) There doesn’t seem to be a formal launch post from OpenAI yet for mobile remote control specifically. What exists right now is code-level evidence in the Android app, plus a trail of recent interface changes and help documentation that make the idea fit the broader product direction. (openai.com) ### What else changed around Codex? Quite a bit, fast. TestingCatalog spotted a refreshed Codex app, new connectors, annotation tools, side-chat hints, and even remote-control references before this latest mobile finding. OpenAI has also been expanding Codex as a multi-surface product — desktop app, web access through ChatGPT, CLI, IDE extensions, and browser-linked workflows. The pattern is clear even if this exact feature is still unreleased. (testingcatalog.com) ### Is mobile doing the coding? Probably not. The wording points to monitoring, reconnecting, and issuing follow-up instructions while the real environment stays on desktop or in the cloud. Think of the phone as the remote for a robot already in the workshop — you can check progress, pause, steer, or resume, but the heavy lifting happens somewhere else. That makes sense for coding agents that depend on repo access, browser sessions, and longer-running execution contexts. (testingcatalog.com) ### Why build it inside ChatGPT? Because ChatGPT is becoming OpenAI’s universal shell. The help docs already say Codex controls can apply across surfaces including ChatGPT web, Atlas, ChatGPT mobile, and Codex, and note workspace permissions for Remote Control through RBAC. That’s the big tell — OpenAI seems to want one identity layer, one permissions layer, and multiple front ends for the same agent workflows. (androidauthority.com) ### Who is this really for? Developers first, but not only developers. Team leads, managers, and anyone supervising long-running agent jobs would benefit from quick mobile check-ins. The more Codex moves toward white-collar orchestration — not just writing code, but coordinating tasks and tools — the more useful a phone dashboard becomes. ### What’s the catch? (help.openai.com) Remote control adds convenience, but it also raises permission and visibility questions. If agents can keep working across devices, admins need clean controls over who can start, monitor, or intervene. OpenAI’s existing RBAC and workspace-level Remote Control settings suggest the company knows that problem is coming with the feature, not after it. The bottom line is simple — OpenAI seems to be closing the last obvious gap in agentic coding. (testingcatalog.com) If Codex is going to run for hours across multiple tools, users need a way to keep a hand on the wheel from anywhere. ChatGPT mobile looks ready to become that wheel. (help.openai.com)