IssueRaiser

Scope Codex VS Code chats to the current workspace/project

### What variant of Codex are you using? IDE Extension cc @etraut-openai, opening this as a fresh feature request per your guidance in https://github.com/openai/codex/issues/17185#issuecomment-4583634793. ### 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

Posted by omry on May 30, 2026, 6:33 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments

github (Software)

Scope Codex VS Code chats to the current workspace/project

omryMay 30, 2026, 6:33 PM

### What variant of Codex are you using? IDE Extension cc @etraut-openai, opening this as a fresh feature request per your guidance in https://github.com/openai/codex/issues/17185#issuecomment-4583634793. ### 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

Comments (0)

No comments yet. Start the discussion.

Comment on this issue