Feature request: Add native microphone and voice dictation to the Codex chat input
Summary
Please add an optional microphone / voice dictation control directly to the Codex chat input, especially in the IDE extension and follow-up workflow used after reviewing generated changes.
Problem
When working with Codex on real projects, follow-up instructions are often detailed and iterative: describe a failed test, clarify expected behavior, list several files to update, or explain a CI/CD scenario. Typing these instructions repeatedly slows down the feedback loop, particularly when the user already has the relevant code and diff open in the editor.
Today, users must rely on external speech-to-text tools, dictate into another application, and then copy the text into Codex. This breaks focus, adds friction, and often provides poor support for languages other than English.
Proposed experience
Add a microphone button near the Codex message composer and the follow-up changes input.
Possible behavior:
- Click or hold to record, then convert speech to editable text before submission.
- Support push-to-talk and an optional keyboard shortcut.
- Let the user review and edit the transcription before sending it.
- Support multilingual dictation and automatic language detection, including Ukrainian.
- Clearly indicate when recording is active.
- Keep the feature optional and disabled until the user activates it.
- Provide transparent privacy controls, including whether audio is processed locally or remotely and whether recordings are retained.
Why this would help
- Faster iteration when reviewing and requesting follow-up changes.
- Less context switching between the IDE, dictation software, and clipboard.
- Better accessibility for users who cannot comfortably type long prompts.
- More natural interaction for complex engineering explanations, debugging context, and CI/CD investigations.
- Stronger usability differentiation for Codex compared with coding assistants that only support keyboard input.
- Potentially higher product engagement because users can provide richer context with less effort.
Example workflow
- Codex proposes changes and shows the diff.
- The user presses the microphone button in the follow-up field.
- The user says: “The implementation is mostly correct, but keep the existing pipeline parameter names, update only the Enlight validation stage, and add a fallback when the previous major version is unavailable.”
- Codex transcribes the request into editable text.
- The user corrects any technical names and submits it.
This would make iterative work with Codex considerably faster without changing the underlying agent workflow.
5 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Environment
openai.chatgpt26.707.71524Acceptance criteria
Nice-to-have enhancements
Thanks for flagging #33221. I reviewed it, and this request is related but not a duplicate.
#33221 asks for a full conversational voice mode in the Codex Desktop app, mainly for spoken interview preparation and project walkthroughs.
This issue is specifically about speech-to-text dictation inside the Codex IDE extension and its existing text inputs, including the follow-up Request changes field. The expected result is editable transcribed text that is never auto-submitted, with multilingual support, keyboard/push-to-talk controls, and privacy handling.
The two requests may share underlying audio/transcription infrastructure, but they target different products, interaction models, and acceptance criteria. I suggest keeping this issue open and linking the implementation where shared components are relevant.
@etraut-openai, thank you for reviewing the request.
Could you please clarify whether the realtime voice mode and microphone controls shipped for Codex Desktop are also planned for the Codex IDE extension for VS Code?
The requirement in this issue is narrower and differs from the Desktop conversational voice mode described in #33221.
We are specifically requesting speech-to-text dictation inside the existing Codex IDE extension inputs:
The Desktop implementation may provide reusable voice infrastructure, but it does not appear to confirm support for these IDE-extension workflows.
Could you please confirm one of the following?
We would mainly like to understand whether the original IDE requirement is covered and where its future progress can be tracked.
@etraut-openai, following up on the IDE-specific dictation request now that we have additional clarification from OpenAI Support.
OpenAI Support case #12971658 confirmed that this request has been logged and escalated as product feedback for the Codex IDE/VS Code extension area. Support also confirmed that there is currently no public documentation establishing that editable dictation should already be available in the VS Code extension, and that the completed Desktop conversational Voice feature does not by itself establish support for this IDE workflow.
I also rechecked the
openai/codexissue tracker today and still could not find another canonical issue clearly tracking editable speech-to-text dictation for the VS Code extension.The requested behavior remains specifically:
Given that #33221 tracked Desktop conversational voice, while this IDE-specific requirement remains separately logged with Support and does not appear to have another public tracker, could you please reconsider the
duplicateclassification for #33548?If there is another canonical issue for this VS Code requirement, please link it here. Otherwise, reopening #33548 would provide a clear public tracking point for the IDE-specific feature request.
Thank you.