Feedback on the ChatGPT Desktop + Codex merge

Open
#35,158 5 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
28/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active

Research direction

The issue names no files, tests, or code entry points. Start by reviewing the desktop mode and floating-chat shortcut behavior described, then define a narrower change; done would require an agreed scope and verified behavior for the selected workflow, including the requested accessibility outcome if Read Aloud is included.

Written by the indexing model from the issue text.

Description

app Broken flow enhancement
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

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.