[macOS] New voice chats initiate using Codex despite selecting ChatGPT operating mode
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.903.61454
What subscription do you have?
Pro - $200
What platform is your computer?
macOS / Darwin 25.5.0 arm64 arm
What issue are you seeing?
I selected ChatGPT explicitly in the dropdown before starting a realtime voice session, which pertained to general knowledge and brainstorming conversation about computer hardware, hosting, and local AI models. I did not request code changes, repository inspection, or other coding work nor did I initiate the chat in a specified codex project.
During this conversation, my displayed remaining weekly Codex allowance dropped from 2% to 1% which was clearly visible as there is a sticky notification box when your usage goes below 10%. I also inquired with the agent which reported that questions were repeatedly being handed to a Codex backend for research and answers.
Furthermore, when I switch tabs from Chatgpt to codex, the voice chat remains on both which is how I've determined that the voice chat was started in Codex. Its my understanding that voice chats using ChatGPT do not consume Codex usage, so I assume that voice chats are starting under Codex even if a user changes to ChatGPT mode.
What steps can reproduce the bug?
Initiate a voice chat after switching from codex to chatgpt operation mode in the Codex desktop app.
What is the expected behavior?
Voice chat should be started under ChatGPT mode. This can be confirmed by checking if the voice chat appears under just ChatGPT or is visible under both ChatGPT and Codex operating modes. If visible under both, the chat was using Codex.
Additional information
UPDATE:
I've had an opportunity to do a bit more testing on this, and this is what I've figured out so far about this bug:
- Regardless of whether ChatGPT or Codex is selected, voice chats always start in Codex/Work mode.
- Even after selecting Chat (rather than Work) in addition to selecting ChatGPT prior to initiating a voice session, it still silently switches to Codex regardless.
- Both the bottom left voice message start button and the integrated button next to message inputs are affected - Neither seem to be able to initiate a voice session using ChatGPT, only Codex.
- I tested nearly the same conversation using voice chat in the iOS app and received about the same results while using chatGPT and no Codex, meaning there were no capability issues on Desktop for it to default to Codex instead of ChatGPT.
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
Reproduce the issue in the Codex desktop app by selecting ChatGPT and Chat, then starting voice chat from both the bottom-left voice button and the button beside the message input. Trace which operating mode each entry point starts and compare whether the session appears under ChatGPT, Codex, or both. Done means voice sessions started in ChatGPT remain in ChatGPT and do not consume Codex allowance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, rust
- Domain
- audio-video-rtc, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 52/100