[Windows] Voice started from Chat is silently routed to Work
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Summary
In the ChatGPT desktop app on Windows, selecting the ordinary Chat experience and starting live Voice silently routes the conversation into ChatGPT Work.
The same account behaves correctly on the web and mobile app: Voice started from Chat remains ordinary Chat. This appears to be specific to the Windows desktop Voice path.
Environment
- Platform: Windows desktop app
- App version: not captured in this report
- Account and plan: not included
- The behavior appears independent of WSL or the selected coding-agent environment
Steps to reproduce
- Open the ChatGPT desktop app on Windows.
- Select ChatGPT, then select Chat rather than Work.
- Start a live Voice conversation.
- Observe that the Voice conversation is routed into ChatGPT Work rather than remaining in ordinary Chat.
- On the same account, start Voice from Chat on the web or mobile app.
- Observe that web and mobile remain in ordinary Chat.
Expected behavior
Starting Voice after explicitly selecting Chat should keep the conversation in Chat. Work should be entered only when the user selects Work or explicitly asks to start a Work task.
Actual behavior
On Windows desktop only, Voice silently routes a Chat conversation into Work. This can change the available context, instructions, and usage behavior. It also makes it difficult to use ordinary Chat Voice independently from Work/Codex.
Additional context
OpenAI's current documentation describes Chat and Work as separate experiences and instructs users to select Chat or Work explicitly:
https://help.openai.com/en/articles/20001275/
Related reports:
- macOS desktop: Chat Voice opening as "Work with ChatGPT" and being gated by the Work/Codex usage pool:
https://github.com/openai/codex/issues/37619 - Windows desktop: recurring Voice failures in local Codex/Work conversations:
https://github.com/openai/codex/issues/42274
A useful diagnostic comparison is that the same account's web and mobile Chat Voice remain in Chat while the Windows desktop app routes Chat Voice into Work.
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 reproducing the Windows desktop app Voice flow after selecting Chat, then compare its routing with the web and mobile behavior described in the report. The issue names no source files or tests, so identify the Windows Voice entry point and verify that starting Voice from Chat remains in Chat rather than entering Work.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100