Feature Request: Separate Chat History Between ChatGPT and Codex

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

Version 26.707.72221

What subscription do you have?

pro

What platform is your computer?

macos

What issue are you seeing?

Hello OpenAI Team,

I would like to submit a feature request regarding the integration between ChatGPT and Codex.

At the moment, ChatGPT conversations and Codex conversations appear together in the same history. While I understand the intention of creating a unified experience, this design creates significant friction for users who use Codex as a dedicated development environment.

For many developers, ChatGPT and Codex serve very different purposes:

ChatGPT is used for general questions, research, brainstorming, and personal conversations.
Codex is used for software development, debugging, and project-specific work.

Mixing these conversation histories makes navigation more difficult, introduces unnecessary noise, and reduces the focus of each workspace. It also creates issues when sharing screens, demonstrating Codex, or simply trying to keep development work separate from general conversations.

A simple configuration option would address this without changing the default experience. For example:

Enable or disable ChatGPT conversations in Codex.
Keep separate conversation histories for ChatGPT and Codex.
Allow users to choose whether histories are synchronized.

The current implementation makes this decision on behalf of every user, even though different users have different workflows. Providing an optional setting would preserve the existing behavior while giving users the flexibility to organize their work in the way that best suits them.

I hope you will consider adding this capability in a future release. I believe many developers would find it valuable.

Thank you for your time and for continuing to improve the platform.

Best regards,

What steps can reproduce the bug?

Feedback ID: no-active-thread-019f612c-ef0c-7d72-823e-95d45671027a

What is the expected behavior?

_No response_

Additional information

_No response_