Skip to content

Project-based Chat Separation (Isolated Chat Context per Project) #17185

Closed

Description

@patel28

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

Activity

  1. added
    extensionIssues related to the VS Code extension
    contextIssues related to context management (including compaction)
    on Apr 9, 2026
  2. removed
    contextIssues related to context management (including compaction)
    on Apr 9, 2026
  3. etraut-openai commented on May 10, 2026

    @etraut-openai
    Contributor

    This feature request hasn't received enough upvotes, so I'm going to close it.

  4. omry commented on May 10, 2026

    @omry

    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.

  5. hipoglucido commented on May 13, 2026

    @hipoglucido

    Implementing this feature would be great actually

  6. omry commented on May 17, 2026

    @omry

    Product direction suggestion:

    1. 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.

    2. 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.

  7. alexeyqu commented on May 20, 2026

    @alexeyqu

    +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.

  8. whatsupbros commented on May 30, 2026

    @whatsupbros

    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.

  9. daxliniere commented on May 30, 2026

    @daxliniere

    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.

  10. etraut-openai commented on May 30, 2026

    @etraut-openai
    Contributor

    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.

  11. locked as resolved and limited conversation to collaborators on May 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestextensionIssues related to the VS Code extension

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions