Feature request: allow separate ChatGPT and Codex account sessions in the unified desktop app

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

Summary

Please allow the unified ChatGPT/Codex desktop app to keep ChatGPT signed into one account while Codex is signed into another.

Problem

Before the unified app, ChatGPT and Codex could be used under different logins. That made it possible to keep ChatGPT on the primary account containing long-lived history and Projects, while switching only Codex to another user account when needed.

In the unified app, logging out of Codex also logs out of ChatGPT, and signing back in changes both surfaces together.

The practical reason for separate Codex login is usage balancing. Multiple user accounts may belong to the same Business plan or organization, but each user may have its own Codex allowance. When one user's Codex usage is exhausted, the user needs to switch Codex to another authorized account without also moving ChatGPT away from the primary account that contains the relevant history and Projects.

Requested behavior

Support concurrent account sessions inside the unified app:

  • ChatGPT remains signed into Account A.
  • Codex can be signed into Account B.
  • Logging out of or switching Codex does not log out of or switch ChatGPT.
  • The UI clearly shows which account is active for each surface.

This does not require separate organizations, billing plans, or workspaces. Both accounts may belong to the same Business plan. The request is simply to decouple the two login sessions so Codex usage can be balanced across authorized users without disrupting ChatGPT continuity.

Example workflow

A user has:

  • a primary ChatGPT account containing years of conversations and Projects;
  • another authorized user account under the same Business plan with available Codex usage.

The desired state is:

  • ChatGPT stays on the primary account;
  • Codex switches to the second account when the first account's Codex allowance is exhausted;
  • ChatGPT history, Projects, and active conversations remain untouched.

Relationship to #34111

Issue #34111 asks for an account switcher and separation of Codex history from ChatGPT history. This request is narrower: a conventional switcher that changes the whole app does not solve the need for ChatGPT and Codex to remain signed into different accounts at the same time.

Desired outcome

Unifying the interface should not force ChatGPT and Codex to share one active login session.

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 1 month ago

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

  • #34111

Powered by Codex Action

sdjaco · 1 month ago

I reviewed #34111 after the duplicate detector flagged it. It is related, but I believe this request is distinct.

#34111 asks for an account switcher and separation of Codex history from ChatGPT history. This issue specifically requests concurrent independent sign-in state inside the unified app: ChatGPT should remain signed into Account A while Codex is signed into Account B.

Both accounts may still belong to the same Business plan or organization. The request is not necessarily for separate billing or separate workspaces; it is for separate active account sessions so switching Codex identity does not also switch or log out ChatGPT.

A conventional account switcher that changes the whole app from Account A to Account B would not solve this workflow. Cross-referencing #34111 because the requests are complementary, but I am leaving this issue open unless maintainers prefer consolidation.

PurpleDevX · 1 month ago

I'm using the ChatGPT Classic app for my ChatGPT account, but when they stop supporting the classic app, I'll have to stop using ChatGPT.

My usage of ChatGPT in recent years depends on two things:

  1. The ability to login to my non-codex account.
  2. Having a global hotkey which toggles an always-on-top popup window.

Without those two features being supported as they always have been by the classic app, using ChatGPT will have too much friction for my daily use.

sdjaco · 1 month ago

This affects my workflow directly, and I want to add a concrete professional use case.

I intentionally use different accounts for ChatGPT and Codex:

  • My primary ChatGPT account contains my long-running projects, conversation history, and accumulated working context.
  • I sometimes need to use a separate business account for Codex when the primary account's Codex usage is exhausted or when billing/usage needs to be separated.

In the unified app, signing out of Codex also signs me out of ChatGPT, and signing back in changes both sessions. That makes it impossible to preserve my ChatGPT project environment while switching only the Codex identity.

Please support independent authentication sessions for ChatGPT and Codex. Logging out of Codex should not log out of ChatGPT, and changing the Codex account should not replace the ChatGPT account.

This is not merely a convenience issue. It is necessary for:

  • separating conversational and coding usage,
  • managing subscription and usage limits,
  • preserving access to long-lived ChatGPT projects and history,
  • using the appropriate organization or billing account for Codex without disrupting ChatGPT.

The global-hotkey, always-on-top popup from the Classic app is also important because it keeps ChatGPT available with minimal friction during daily work. Losing both independent account sessions and the popup workflow would be a substantial regression for power users.