You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Project-based Chat Separation (Isolated Chat Context per Project) #17185
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
Work on Project A in one chat
Switch to Project B (different task/codebase)
Accidentally continue in Project A chat
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
Reacted by Omry Yadan, Víctor García, Yufeng Zheng, Michał Walenciak, Saunak and Denis Savenko
Here is a vote. just came for it.
Please reopen. operating on multiple projects at the same time is very confusing because the all the chats are mixed up.
For my use case, I am specifically getting bit by vscode codex plugin. Not sure if this is the same surface here, but its the same issue.
If not already there, associate project name or directory with each chat thread. At minimum this is the vs code project (what directory we opened vscode on. Even better if it also includes the actual sub-project, in case a single window contains multiple projects.
in the UI:
group chats by project.
if there is only one project, do not show presentation.
If there are 2 or more, visually separate and group chats per project.
We can put the chats of the current active project at the top and have the chats for other projects folded below to prevent confusion. maybe even hide them completely.
@etraut-openai
I am willing to give it a shot and send a PR if there is support for this from the team.
+1 -- as someone who is switching from Cursor to Codex/VSCode, this is the feature I miss the most.
It is very useful to see chats related to a particular project when coming back to it after a few days of a different context.
Codex CLI already has this isolation functionality by working directory, which is always on by default. To see all chats, there's codex resume --all option, and if you choose a thread from a different directory, it even asks if it should switch the working directory of the thread to the current one.
This means that this isolation logic is already there and is only needed to.be integrated into VS Code extension. The concept of working directory exists in VS Code and can be reused here as well.
This issue has been closed because it didn't receive enough upvotes. If you'd like to see a similar feature, please create a new feature request with a new title and description.
Activity
github-actions commentedon Apr 9, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
etraut-openai commentedon May 10, 2026
This feature request hasn't received enough upvotes, so I'm going to close it.
omry commentedon May 10, 2026
Here is a vote. just came for it.
Please reopen. operating on multiple projects at the same time is very confusing because the all the chats are mixed up.
For my use case, I am specifically getting bit by vscode codex plugin. Not sure if this is the same surface here, but its the same issue.
hipoglucido commentedon May 13, 2026
Implementing this feature would be great actually
omry commentedon May 17, 2026
Product direction suggestion:
If not already there, associate project name or directory with each chat thread. At minimum this is the vs code project (what directory we opened vscode on. Even better if it also includes the actual sub-project, in case a single window contains multiple projects.
in the UI:
group chats by project.
if there is only one project, do not show presentation.
If there are 2 or more, visually separate and group chats per project.
We can put the chats of the current active project at the top and have the chats for other projects folded below to prevent confusion. maybe even hide them completely.
@etraut-openai
I am willing to give it a shot and send a PR if there is support for this from the team.
alexeyqu commentedon May 20, 2026
+1 -- as someone who is switching from Cursor to Codex/VSCode, this is the feature I miss the most.
It is very useful to see chats related to a particular project when coming back to it after a few days of a different context.
whatsupbros commentedon May 30, 2026
Codex CLI already has this isolation functionality by working directory, which is always on by default. To see all chats, there's
codex resume --alloption, and if you choose a thread from a different directory, it even asks if it should switch the working directory of the thread to the current one.This means that this isolation logic is already there and is only needed to.be integrated into VS Code extension. The concept of working directory exists in VS Code and can be reused here as well.
daxliniere commentedon May 30, 2026
Yes, agree this is a very useful thing. When I'm working on an Arduino project, I don't need to see web development threads.
etraut-openai commentedon May 30, 2026
This issue has been closed because it didn't receive enough upvotes. If you'd like to see a similar feature, please create a new feature request with a new title and description.