Scope Codex VS Code chats to the current workspace/project

Resolved 💬 2 comments Opened Jul 17, 2026 by mikasa-code Closed Aug 6, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What variant of Codex are you using?

vscode Extension

What feature would you like to see?

In the Codex VS Code extension, chat/thread history should be scoped, grouped, or filtered by the current workspace/project.

Right now, chats from different projects appear together in one shared history list. When working across multiple repositories, VS Code windows, remote workspaces, WSL/SSH sessions, or unrelated codebases, it becomes easy to resume the wrong thread or confuse which chat belongs to which project.

This creates a real workflow problem because Codex threads carry project-specific context. Accidentally continuing a thread from another project can lead to irrelevant suggestions, wrong assumptions, and extra mental overhead.

A useful MVP could be:

Associate each thread with its originating VS Code workspace folder or working directory.
Show current-workspace threads first in the extension history.
Hide, collapse, or visually separate threads from other workspaces.
Provide an “all threads” view or toggle for users who intentionally want global history.
Preserve existing thread rename/archive behavior.
This does not need to introduce a full project-management system. The most important behavior is that when I am in Project A, I should not have to scan through chats from Projects B, C, and D to find the relevant Codex thread.

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 1 month ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #33734

Powered by Codex Action

AlexSoare · 25 days ago

Yeep, it would be great to have this. This is one thing I miss from Copilot (also the way Copilot was showing the agent modifications, but that is another discussion).

Even skills are global to all projects/workspaces, and sometimes, if a project/workspace name looks similar to another where I've specifically created a skill for, upon starting a new conversation, GPT tries to use that skill first, and I have to tell it we are not in that project for which the skill is made.