Skip to content

Feedback on the ChatGPT Desktop + Codex merge #35158

Open

Description

@Brad-M2K

What variant of Codex are you using?

App combined chat gpt new desktop app

What feature would you like to see?

Feedback on the ChatGPT Desktop + Codex merge

I was actually one of the people who liked the original decision to combine ChatGPT Desktop and Codex into one application. I thought it was heading in the right direction and just needed polishing.

Unfortunately, after the recent updates, I feel the experience has become much more confusing.

Separate the conversation mode from the application mode

I don't think users should have to switch the entire application between "ChatGPT", "Work Agent" and "Codex".

Instead, every conversation should simply have a mode.

For example:

  • ChatGPT
  • Work Agent
  • Codex

That way I could have different conversations in different modes without changing the whole application.

At the moment I constantly find myself switching the application's mode just because I want to ask a normal ChatGPT question, which feels unnecessary and breaks the flow.

The original floating chat worked much better

Originally, pressing Command + Option + N always opened a floating ChatGPT window.

This worked really well because I could:

  • Keep Work Agent or Codex open for development.
  • Instantly open a normal ChatGPT conversation alongside it.
  • Continue working without changing modes.

It felt like the best of both worlds.

The floating chat now feels broken

Since the recent changes, the floating chat has become much less usable.

Current issues include:

  • It does not appear with Command + Option + N if the sidebar is collapsed.
  • It frequently opens a brand new conversation instead of continuing the existing floating chat.
  • Pressing the shortcut again no longer closes it—you have to press Escape instead.
  • The behaviour feels inconsistent depending on the current mode.

This used to be one of my favourite features.

I think the wrong problem was solved

It feels like these changes were made because some users wanted the old separate ChatGPT application back.

However, those users could simply open a floating ChatGPT window and essentially get that exact experience already. And most people probably did not notice but i did you could press an still can in floating chat open in a new window and you basically got the echat gpt old desktop app again with a nicer look which is good for separate workflows and having a chat in another screen/ space while having chat gpt app itself just doing its thing not needing to move. I hate friction!

Instead of improving the unified workflow, it now feels like the app has become fragmented again.

The original direction felt modern. It just needed refinement.

Improvements I would have preferred

Rather than changing the overall workflow, I think improvements like these would have been much more valuable:

  • Better focus management for the floating chat.
  • When the floating chat is active, Command + N should create a new ChatGPT conversation inside the floating window—not in the Codex or Work Agent conversation behind it.
  • If the floating window is focused, keyboard shortcuts should apply to it.
  • When it loses focus, it could optionally hide itself until reopened.
  • Pressing Command + Option + N again should toggle the floating chat open and closed.
  • Also pressing shortcuts like so should be summonable even when app is not focused.

These feel like natural quality-of-life improvements that preserve the original workflow.

Read Aloud

One feature I really miss from the old ChatGPT desktop app is Read Aloud.

I have Attention Deficit Hyperactivity Disorder, and after spending hours developing software I often struggle to read long responses. I much prefer typing my prompts but listening to the replies.

The mobile ChatGPT app and the previous desktop app both handled this really well with high-quality voices.

Please consider bringing Read Aloud back to the desktop application. It was genuinely one of the most useful accessibility features for me.

Overall

I genuinely preferred the original unified application.

To me, it felt like the future of ChatGPT and Codex in one place.

Now it feels like the workflow has become more confusing, with different application modes competing instead of conversations simply having different capabilities.

I hope you'll consider revisiting the original direction and refining it rather than moving away from it. You were really on to something and do not let the few grumpy users who don't know how to change who complain like Karens stop you from breaking moulds. out of all the users the app gets did all complain? or just like hundreds out of what millions?

Additional information

No response

Activity

  1. github-actions commented on Jul 24, 2026

    @github-actions
    Contributor

    Potential duplicates detected. Please review them and close your issue if it is a duplicate.

    Powered by Codex Action

  2. mjdaved commented on Jul 25, 2026

    @mjdaved

    yes i also would like the feature of Read Aloud because i have difficulty of reading long response as i have dyslexia.

  3. bcoffee0630 commented on Jul 28, 2026

    @bcoffee0630

    I agree with the core idea in this issue: the ChatGPT/Codex mode should belong to a conversation rather than the application as a whole.

    I encountered a related multi-window problem and found this issue while preparing a separate report.

    Current design problem

    1. Open the unified ChatGPT/Codex desktop app.
    2. Create a second window with ChatGPT > File > New Window.
    3. Keep a Codex task running in one window.
    4. In the second window, use the sidebar to switch from Codex to ChatGPT.
    5. All other open windows switch to ChatGPT as well.

    Because switching the mode in any window changes every other window, separate windows cannot be used for separate ChatGPT and Codex workflows. At present, the product mode is effectively coupled at the application level.

    Minimum fix and preferred direction

    At minimum, each window should retain its own ChatGPT/Codex mode. This would let me keep Codex running in one window while using ChatGPT in another to research supporting information in a specific Project.

    However, the conversation-scoped design proposed in this issue is better than that minimum correction. It would both remove the current cross-window coupling and make the mode follow the user's actual unit of work, improving flexibility whether conversations are displayed in one window or several.

    This matters because ChatGPT and Codex serve different parts of my workflow, and their usage limits are tracked separately. Using Codex for ordinary supporting research is not the right tool fit and unnecessarily consumes Codex usage.

    A product design change along these lines—at least independent modes per window, and ideally the conversation-scoped approach proposed here—would provide a much better experience.

  4. Yogev-Navina commented on Aug 3, 2026

    @Yogev-Navina

    I’m experiencing a related issue in the combined ChatGPT desktop app.

    Actual behavior: the configured “Popout window hotkey” always opens Codex Quick Chat.

    Expected behavior: the shortcut should open regular ChatGPT Chat, follow the currently selected experience, or provide a setting to choose between Chat, Work, and Codex.

    At present, I cannot find any setting that changes the pop-out destination.

  5. vecelli12 commented on Aug 30, 2026

    @vecelli12

    Confirming this on ChatGPT Desktop 26.825.41651 on macOS arm64 (tested 2026-08-30).

    Reproduction:

    1. Stay in ChatGPT / Chat mode with the left sidebar visible.
    2. Press Cmd + Option + N.
    3. Nothing happens; the shortcut fails silently.
    4. Switch to Codex mode with Ctrl + 3.
    5. Press the same shortcut; Quick Chat opens immediately.

    This makes Quick Chat unavailable exactly where it is most useful to me: while reading a long regular ChatGPT conversation. I want to ask a short, unrelated question in a small overlay and then return to the original thread without navigating away, losing my scroll position, or having to search through the long conversation again.

    Expected behavior: Quick Chat should be invokable from Chat mode as well as Codex mode. At minimum, the shortcut should not silently fail; the interface should clearly explain any mode restriction.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Broken flowappIssues related to the Codex desktop appenhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions