Feature request: add voice conversations to Codex Mobile Remote
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- ios, rust
- Domain
- audio-video-rtc, mobile-dev
Research direction
Start by reading the existing Codex Mobile Remote behavior and the referenced Remote Voice connection report. Trace how a paired iPhone currently joins a live Mac task, including context, permissions, approvals, and status updates. Done means Remote supports the requested real-time voice conversation with streaming responses, interruption, spoken updates, and existing confirmation safeguards.
Written by the indexing model from the issue text.
Description
Request
Please add first-class Voice support to Codex Mobile Remote, so a paired iPhone can join the same live Codex conversation running on a Mac host through natural, real-time speech.
Why this matters
Remote already brings the useful local context to the phone: active threads, repositories, skills/plugins, task state, tool permissions, and approvals. The remaining gap is that it is text-first. For time away from a desk—especially walking between meetings or hands-free use while driving—voice is the natural way to steer an ongoing task without losing that context.
A generic ChatGPT Voice conversation is not an equivalent workaround because it does not share the live local Codex environment.
Desired experience
- Start or continue a voice conversation from a paired device in Mobile Remote.
- Send each spoken turn to the same live Codex task on the Mac, retaining its context, tools, and permission model.
- Hear streaming responses and interrupt naturally.
- Receive spoken status updates for active workers and pending approvals.
- Keep consequential actions behind the existing confirmation surface.
Success criterion
A user can leave the desk, open Remote on an iPhone, and have the same context-aware Codex conversation they would have had on the Mac—without rebuilding context or using a separate control plane.
Scope note
This is a feature request, not a report of a mobile Voice connection failure. It complements the existing Remote Voice connection report by describing the product behavior needed once the capability is broadly available.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- Avg merge
- 1m
- Merged PRs (30d)
- 1k
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openai/codex
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug CLI windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
macOS sandbox blocks hw.optional.arm64 sysctl, causing Flutter to misdetect Apple Silicon as x64 Openbug CLI sandbox
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug CLI TUI
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
CLI config enhancement skills
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
A-linter
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oxc-project/oxc#26863 ·