ChatGPT Desktop Voice launches as Work/Codex and loses ChatGPT memory

Environment

• Platform: macOS
• App: New ChatGPT/Codex Desktop App
• Version: 26.818.31338
• Release date: Aug 20, 2026
• Account: ChatGPT Plus
• Feedback ID: no-active-thread-01a02563-24ce-7051-b59b-2ebffbfe8ec4

Bug description

I am experiencing a reproducible Voice routing/state issue in the new desktop app.

When ChatGPT is explicitly selected in the upper-left mode selector, starting a new Voice Chat creates a conversation labeled Work in the sidebar.

During that Voice session, the assistant says it is operating in Codex mode and cannot access the ChatGPT memory/personal context that is available in normal ChatGPT conversations.

This happens even though ChatGPT — Create, learn, and explore is visibly selected, not Codex — Build, debug, and ship.

Steps to reproduce

1. Open the new desktop app.
2. Select ChatGPT in the upper-left selector.
3. Start a brand-new conversation.
4. The Voice waveform button is initially visible.
5. Start a Voice Chat.
6. Ask a question whose answer is already available through ChatGPT memory, for example: “What is my name and date of birth?”
7. Voice says it does not have the information.
8. When asked why it cannot access information that ChatGPT normally remembers, Voice indicates that it is operating in Codex mode.
9. In the sidebar, this newly created Voice conversation is labeled Work, despite having been launched while ChatGPT was selected.

Cross-platform comparison

Using the same account and the same memory test:

• Desktop text Chat: works correctly.
• ChatGPT Voice in web browser: works correctly.
• ChatGPT Voice on mobile: works correctly.
• Voice in the new macOS desktop app: memory/context is unavailable and the session appears as Work/Codex.

This appears to isolate the issue to Voice routing in the new desktop application rather than an account-level memory problem.

Possibly related UI bug

There is a second reproducible behavior:

1. Create a new conversation with ChatGPT selected.
2. Before sending anything, the Voice waveform button is available.
3. Send a text message instead.
4. After the conversation has started as text, the Voice waveform button disappears.
5. Only the dictation microphone remains.

As a result, I cannot transition an existing ChatGPT text conversation into Voice.

Additional evidence

Under Settings → Voice, the application displays:

“Choose the voice Codex uses for new voice chats”

I also have a screenshot showing simultaneously:

• ChatGPT selected in the upper-left selector;
• a normal conversation labeled Chat;
• a New voice chat conversation labeled Work;
• the Voice waveform button absent from the existing Chat conversation.

Expected behavior

When ChatGPT is selected, starting Voice should launch the normal ChatGPT Voice experience and retain access to the applicable ChatGPT memory/context, as it does on web and mobile.

An existing ChatGPT text conversation should also allow switching to Voice if that functionality is supported.

Actual behavior

ChatGPT selected → Start Voice → session becomes Work → Voice reports Codex context → ChatGPT memory unavailable

while:

ChatGPT selected → Start by text → session remains Chat → Voice waveform disappears → only dictation remains

This looks like a possible routing/state issue between ChatGPT Chat, ChatGPT Voice, Work, and Codex Voice.

Possibly related issue

Possibly related: #38955 reports similar incorrect Chat → Work/Codex Voice routing on Windows. However, this report reproduces the issue on macOS and additionally documents loss of ChatGPT memory/context in Voice and disappearance of the Voice waveform button after starting a conversation by text.
The corresponding diagnostic feedback/session logs were already uploaded under:

Feedback ID: no-active-thread-01a02563-24ce-7051-b59b-2ebffbfe8ec4

No source file, test, or entry point is identified in the report. First reproduce the macOS flow with ChatGPT selected and review the uploaded diagnostic session for feedback ID no-active-thread-01a02563-24ce-7051-b59b-2ebffbfe8ec4; the fix is confirmed when Voice stays in ChatGPT, retains applicable memory/context, and the reported text-to-Voice behavior is resolved.