ChatGPT Voice comes to Codex on iOS

The iOS feature isn't Codex running natively with a microphone on the phone - it's a paired-remote setup. Once a phone is linked to a desktop host running the Codex app, ChatGPT Voice on iOS routes spoken requests through OpenAI's GPT-Live model to direct Codex tasks on that connected machine ^[1]. That pairing mechanic isn't new: OpenAI first shipped Codex remote control on mobile in May 2026, letting iPhone, iPad, and Android users scan a QR code generated by the Codex Mac app to monitor running threads, approve commands, and review diffs and test results from their phone ^[2]. At the time, pairing only worked with the macOS build of Codex, with Windows support promised as coming soon ^[2]. What's new on July 23 is that this existing remote channel now carries voice, not just text and taps - a developer can say something like 'start a Codex task to run the tests and investigate anything that doesn't pass' from their phone and have it kicked off on the paired desktop ^[1].

Fortune frames the voice launch as part of OpenAI's push to keep Codex ahead of Anthropic's Claude Code in the agentic-coding race ^[3], arriving two weeks after Codex was folded into a broader ChatGPT Work product on July 9 - a merger Fortune reports grew the tool's weekly user base from about 5 million to roughly 10 million ^[3]. Thibault Sottiaux is named as overseeing Codex following that merger ^[3]. Adding a full-duplex voice layer that can listen and speak while coordinating background tasks lets OpenAI pitch orchestrating multi-threaded coding jobs, reviewing PRs, and debugging by voice as a differentiator beyond typing ^[3], building on the GPT-Live model OpenAI introduced roughly two weeks earlier as a general-purpose voice layer for ChatGPT rather than something built for Codex alone ^[4].

Voice access comes with real constraints worth knowing before leaning on it. Conversations draw from a separate, plan-dependent allowance measured in rolling five-hour windows, distinct from ordinary Codex usage, and only one voice chat can be active at a time across the desktop app ^[1]. Crucially, any Codex task that Voice kicks off still consumes the underlying Codex usage budget on top of that - talking to Codex changes the input method, it doesn't create free compute ^[1]. The same July 23 update layered in screen context on macOS (saying 'Take a look at this' shares a screenshot of the current window), gated behind Screen and System Audio Recording and Accessibility permissions ^[1], though that particular capability is scoped to the desktop app rather than the iOS pairing.

Not everyone welcomed the update as a leap forward. AI commentator Chubby (@kimmonismus) called the release modest relative to the buildup, noting the concrete additions were voice, macOS screen context, and multi-folder projects, and expressed disappointment that a rumored faster inference tier didn't materialize: 'I really hope they release more than this. They hyped today's release up quite a bit.' That tension between anticipation and delivery echoes on r/codex, where discussion splits between developers excited about accessibility and hands-free use cases and others who argue voice is the wrong interface for precise coding work - it's easier to type an exact command or JSON payload than to speak it, and a misheard instruction risks triggering something destructive. Several threads also tie the launch back to ongoing frustration over Codex usage limits, treating voice more as a distraction than the feature developers were actually asking for.