Codex Work Still Pollutes Main ChatGPT History + No Account Switcher = Persistent User Frustration

The issue names no files, tests, or entry points. Begin by locating the history and account-management areas, then determine whether the requested separation and account switching fit this repository. Done means Codex activity can stay out of the main history unless selected and users can switch accounts without logging out.

What version of the Codex App are you using (From “About Codex” dialog)?

Latest (integrated into ChatGPT interface)

What subscription do you have?

ChatGPT Pro / Teams (paid user)

What platform is your computer?

Windows 10 64

What issue are you seeing?

This is getting ridiculous.

OpenAI continues to classify Codex coding sessions as generic "Work" feature activity, forcibly injecting them into the main ChatGPT conversation history. Users explicitly do not want their developer tool usage polluting their regular chat threads.

The product team has apparently decided that developers don't deserve clean separation between casual ChatGPT usage and serious coding work. Every Codex interaction becomes permanent noise in the primary history — a privacy nightmare and usability disaster that affects power users daily.

Meanwhile, basic multi-account functionality (an Account Switcher) — something virtually every other major platform implemented years ago — remains missing. This forces awkward workarounds for users managing personal, work, and experimental accounts.

This isn't an edge case. This is fundamental product negligence.

• Codex is marketed as a professional coding tool.
• Treating its output like casual chit-chat shows a complete disconnect from how developers actually use the product.
• Forcing history pollution in "ChatGPT mode" demonstrates tone-deaf prioritization.

Please fix the classification logic, add proper workspace isolation (or at minimum a toggle to exclude Codex from main history), and implement a functional Account Switcher.

Paid users expect better than this half-baked integration. Stop treating serious coding work as an afterthought.

What steps can reproduce the bug?

Feedback ID: no-active-thread-019f787f-9e0a-7513-aa44-8978ec401336

What is the expected behavior?

Expected behavior is straightforward and should have been implemented from day one:

1. Codex coding sessions should never automatically appear in the main ChatGPT conversation history unless the user explicitly chooses to save them.
   Users need clean separation between casual ChatGPT usage and professional developer tool work.

2. A proper Account Switcher must exist in the interface, allowing instant switching between multiple accounts without logging out or using multiple browser profiles.

3. Users should have granular controls (toggles, workspaces, or separate history modes) so that "Work"/Codex activity does not pollute personal or primary chat histories.

This is basic product hygiene for a tool targeted at developers and power users. Treating Codex as just another chat thread demonstrates a fundamental misunderstanding of user workflows.

Additional information

This issue has been repeatedly raised by the community yet remains unresolved.

Forcing Codex output into the main ChatGPT history is not just annoying — it's actively harmful to user experience and privacy. Many professionals use ChatGPT for both personal and work-related tasks. Mixing them creates clutter, security concerns, and makes the product feel amateurish.

The continued absence of an Account Switcher in 2026 is frankly embarrassing for a company at OpenAI's level.

Please treat this as a serious product deficiency rather than a minor annoyance. Paid users expect the platform to respect how we actually work.