### What issue are you seeing? Codex Voice no longer starts because it refuses to establish a connection. ### Context - The Codex app was reinstalled after repeated computer freezes/restarts. - Codex worked again after the reinstall, but Voice subsequently stopped connecting. - Windows may change the default microphone and speaker after a restart; the intended devices were selected again. - Restarting Codex did not restore Voice connectivity. ### Expected behavior Codex Voice should connect

Voice fails to connect after reinstall on Windows

Open 💬 3 comments Opened Jul 30, 2026 by mjferdinandus-debug

What issue are you seeing?

Codex Voice no longer starts because it refuses to establish a connection.

Context

The Codex app was reinstalled after repeated computer freezes/restarts.
Codex worked again after the reinstall, but Voice subsequently stopped connecting.
Windows may change the default microphone and speaker after a restart; the intended devices were selected again.
Restarting Codex did not restore Voice connectivity.

Expected behavior

Codex Voice should connect and use the selected Windows microphone and speaker.

Additional information

The exact error message and app version were not available at the time of filing.

View original on GitHub ↗

3 Comments

mjferdinandus-debug · 29 days ago

Diagnostic update: Bluetooth media routing restored on Android

I found and resolved a closely related audio-routing symptom on my Samsung Galaxy A33 with a connected Bose SoundLink Revolve II.

The Bluetooth connection itself was active, but media/voice audio continued to play through the phone. The working sequence was:

Open Media output on the Samsung phone.
Open the media-session controls shown there.
Tap Resume and then the Play button.
Android reactivated the media session and routed the sound to the connected Bose speaker.

The apparent chain was:

Bluetooth connected → media session inactive/paused → Android kept audio on the phone → Resume/Play reactivated the session → output routing switched to the Bose speaker.

This points to a media-session/output-routing state, rather than a Bluetooth codec problem. A codec such as SBC or AAC handles the audio stream after routing is active; it does not itself select the output device.

This may help other users who see a connected Bluetooth speaker but still hear audio from the phone.

Important: this workaround was confirmed on Android. It does not yet prove that the separate Windows Codex Voice connection failure described in this issue is resolved, so I am leaving the Windows issue open until that behavior is retested.

mjferdinandus-debug · 13 days ago

Follow-up

Could the Codex team please take another look at this issue?

The issue remains open. The Android Bluetooth media-routing workaround I documented above was useful for that separate symptom, but it does not confirm a fix for the Windows Codex Voice connection failure described in this report.

Please let me know if logs, the exact error message, or current app/version details would help with further diagnosis.

mjferdinandus-debug · 13 days ago

Follow-up — issue still unresolved

This problem is still occurring and, to date, no solution has been found. The issue is on my Android phone: Codex Voice is not connecting or routing audio to my Bose Bluetooth speaker. Codex Voice does work on my PC, so the problem appears to be specific to the Android phone/Bose Bluetooth-speaker connection.

I would appreciate help identifying a solution so that I can use Codex Voice with my Bose Bluetooth speaker on my Android phone. Please let me know if current logs, the exact error message, or Android/app details would help with further diagnosis.