Bring back separate ChatGPT and Codex desktop workflows (or independent windows)

Open 💬 2 comments Opened Aug 5, 2026 by NaitSide
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What variant of Codex are you using?

Desktop App (Unified ChatGPT + Codex)

What feature would you like to see?

Before the unified desktop app, I had a workflow that significantly improved my productivity.

I used ChatGPT as my architecture and discussion partner, while Codex acted as my execution engine.

This wasn't simply about having two applications.

It was about separating thinking from execution.

On my dual-monitor setup, ChatGPT was always open on one screen, and Codex was open on the other.

I discussed architecture, reviewed implementation ideas, validated approaches, and explored edge cases in ChatGPT.

At the same time, Codex was connected to my local development environment, Docker containers, SSH sessions, and project files, actively implementing those ideas.

While Codex was working, I never had to wait.

I continued discussing another feature, another project, reviewing documentation, or solving a completely different problem in ChatGPT.

When Codex finished, I copied its report into ChatGPT for review, discussion, and validation before sending the next task back to Codex.

This created a natural engineering workflow:

  • ChatGPT helped me design.
  • Codex implemented the solution.
  • ChatGPT reviewed and challenged the implementation.
  • Then I sent the refined task back to Codex.

It felt like working with two different specialists in parallel.

The old workflow naturally separated thinking from execution. ChatGPT was my architect and reviewer, while Codex was my engineer.

After the merge, this workflow disappeared.

Now everything lives inside a single application, forcing constant context switching instead of allowing parallel work.

This isn't just a UI preference.

It is a measurable productivity regression.

When Codex is executing long-running tasks, I no longer have an independent workspace dedicated to planning, architecture discussions, or other projects.

The unified interface may be simpler for new users, but it removed an extremely efficient workflow that many professional users relied on every day.

My request

Please restore one of these workflows:

  • Separate ChatGPT and Codex desktop applications.
  • Independent ChatGPT and Codex windows.
  • Any mode where both can stay open simultaneously as independent workspaces.

Please don't remove workflows that experienced users have built around.

Even an option to open ChatGPT and Codex as separate windows inside the unified application would completely solve this problem.

Additional information

This workflow was especially valuable because I often worked on multiple projects simultaneously.

While Codex was implementing one feature, I continued discussing another project in ChatGPT.

The merge unintentionally turned two parallel workspaces into one shared workspace.

The result is more context switching, less multitasking, and lower productivity.

I understand why a unified application is useful, but please preserve the ability for power users to work with ChatGPT and Codex independently.

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 22 days ago

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

  • #35917
  • #35970

Powered by Codex Action

NaitSide · 22 days ago

These issues are related, but this request is not a duplicate.

#35917 and #35970 describe bugs where an existing “open in a new window” or Quick Chat feature does not work correctly.

This request is about restoring a persistent parallel workflow: keeping ChatGPT and Codex open simultaneously as independent workspaces, ideally on separate monitors, so one can be used for architecture and review while the other executes long-running tasks.