This is not mentioned anywhere and it’s a core feature that I use all the time. Currently on 26.422.21637
Firstly welcome to the community @drdan .
Can you please clarify what is not mentioned?
Thanks for clarification. The voice input should still be there, at least, I couldn’t find any evidence stating otherwise. Can I hear out that in a previous version the voice input worked flawlessly?
I guess the feature is still not that stable for everyone. Did you already try the shortcut (Ctrl + M) out? Or did you try to restart the app immediately after granting permission?
Yes, voice input worked flawlessly in the previous version/current account a few days ago. I used the microphone icon in the Codex composer to dictate messages directly.
Current behavior:
- The microphone icon is no longer visible in the Codex composer.
- The official shortcut Ctrl + M does not start dictation.
- Instead, Ctrl + M minimizes the Codex app window.
- I already restarted the app after checking/granting microphone permissions.
- Windows microphone access is enabled, including access for desktop apps.
- Already reinstalled Codex app and logout/login back
- My Plus subscription expired a few days ago and I renewed it
- Voice input disappeared after that period.
- I am signed into the same account.
Thank you for providing a list with things you already tried.
Voice input should be enabled/disabled on the server side. You mentioned you extended the Pro subscription.
Did you try to Logout and Login after you extended the Pro subscription?
Did you check the Settings? If under Feature: “Voice transcription” is enabled?
Yes, I logged out and logged back in after renewing the subscription.
I also fully quit the Codex app, reopened it, and signed in again with the same account and same sign-in method. I also tried to reinstall not only Windows Store app but also win32 version, nothing changes.
However, I need clarification about the “Voice transcription” setting, what exactly do you mean? I don’t see anything like that in my Codex app settings. If you mean config.toml file - I already added there “voice_transcription = true” but it doesn’t help also.
Thanks again for clarification.
Have you tried to go back to a previous build version where the voice transcription was working, for example: 26.304?
Could you please clarify where can I find it?
Latest version is 26.422.30944 (2080) and that version is showing the ‘microphone’ icon which enables voice transcription flawlessly.
This indicates @drdan that you are not yet using the finest and greatest version of Codex
I have the same issue on macOS.
Codex App version: 26.422.30944 (2080)
Symptoms:
-
The microphone / voice dictation button is missing from the composer.
-
Holding Ctrl + M does not start dictation.
-
The issue appeared after updating the Codex App.
-
I fully reinstalled the app.
-
I logged out and logged back in.
-
macOS microphone permission is enabled for Codex.
-
Rate limits are visible, so the account appears to be authenticated.
Important detail: another user reported that 26.422.30944 (2080) shows the microphone icon and voice transcription works for them. So this does not look like an outdated app version issue. It looks more like an account-side feature flag, rollout, or regression.
Could the Codex team please check whether voice transcription is being disabled server-side for some accounts?
I got a reply from the official support team:
“Based on what you’ve shared so far, this behavior may be related to an issue we’ve noted internally and are actively reviewing”
So they know about the issue, but they won’t be able to provide ongoing updates or specific timelines regarding resolution ![]()
Anybody has any updates regarding this issue? It’s been 3 weeks already and I didn’t get any reply from the support team anymore and the voice input option is still not available =\
Has anybody solved this issue? I have the same problem on Windows.
Changing the IP helped me. I used VPN. I switched from my location to Japan, and the microphone appeared.
For me it automagically solved itself about 4 app updates after I posted this. Working with no problems on 26.513.31313 (2867) - but still it’s unbelievable how poorly tested this app is

