Mobile: resume live voice in the same existing task after a dropout
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What variant of Codex are you using?
Mobile Codex live voice. Mobile OS and app version were not provided.
What feature would you like to see?
Allow a dropped live Codex voice session to be restarted or resumed in the same existing task on mobile.
Reported sequence:
- Start a live Codex voice session on mobile.
- The voice session drops.
- Reopen the existing chat/task.
- Only text input/dictation is available; there is no way to restart or resume live Codex voice within that same task.
Expected behavior: provide a Resume voice or Start voice action in the existing task after a dropout, retaining the task's conversation context so the spoken conversation can continue.
Impact: a dropout breaks conversational continuity because the user cannot continue in live voice in the same task. Dictation does not restore the live voice session.
Additional information
Submitted on the user's behalf with explicit authorization, based on their reported experience; not independently reproduced. No logs or session transcripts are attached.
Related issue: #36537 concerns draft loss and reconnect problems on Android. This request specifically concerns the missing ability to restart live voice in the same existing mobile task after a dropout.
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.
Research direction
Start by tracing the mobile live voice session lifecycle and how an existing task is reopened after a dropout; the issue names no files, tests, or entry points. Done means an interrupted live voice session can be restarted or resumed in the same task while retaining its conversation context, with coverage for the reported sequence.
Written by the indexing model from the issue text.
Assessment
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100