codex - 💡(How to fix) Fix Project-based Chat Separation (Isolated Chat Context per Project) [1 comments, 2 participants]

What variant of Codex are you using?

Ide Extension

What feature would you like to see?

Hi OpenAI Team,

I'm using Codex for development across multiple projects (e.g., Android, backend, prompt engineering), and I'm facing frequent issues due to lack of project-based chat separation.

Problem

Currently, all chats exist in a single flat list with no project-level isolation. This makes it very easy to accidentally send messages in the wrong chat while switching between projects.

Since Codex relies heavily on chat context, this leads to incorrect or confusing outputs when context from another project is used unintentionally.

Steps to Reproduce

1. Work on Project A in one chat
2. Switch to Project B (different task/codebase)
3. Accidentally continue in Project A chat
4. Codex uses wrong context → incorrect responses

Impact

• High risk of mixing contexts between different projects
• Incorrect code generation and debugging suggestions
• Reduced productivity and increased mental overhead

Suggested Solution

Introduce project-based chat separation, such as:

• Ability to create/select a "Project"
• Chats grouped under each project
• Context isolated per project
• Optional: project-level memory or instructions

This would significantly improve developer workflows and reduce context-related errors.

Thanks!

Additional information

No response