VS Code extension shows the same global 51 conversations in every workspace
I am experiencing the same issue（#3550） in the current VS Code Codex extension.
Every VS Code project shows the same 51 conversations. This is not caused by
opening a parent directory or the wrong workspace: I open each repository in
its own pinned VS Code window.
I inspected the local Codex state database:
- 93 total threads
- 20 distinct
cwdvalues - only 4 threads belong to the currently opened repository
- nevertheless, the extension displays the same 51 conversations in every repository
This confirms that workspace detection and per-thread cwd metadata are
correct, but the VS Code conversation list is not filtering by the active
workspace. The usability problem becomes progressively worse as global
conversation history accumulates.
In-product feedback IDs:
- 019f6010-c0fc-7031-97b6-d2f6e7c40fd4
- 019f6e18-144a-7672-9309-a6612fa03193
VS Code Codex extension version: 26.609.30741
Platform: Windows + WSL
Related issues:
- #3550 described the same workspace-scoping problem, but it is closed and the
problem is still reproducible in the current extension.
- #15368 documents a 50-thread recent-conversation page limit, which may explain
why the extension displays 51 conversations.
2 Comments
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.
I am experiencing the same issue in the Windows VS Code Codex extension (version 26.5727.51351).
When I open a workspace, the Codex sidebar still shows sessions created in unrelated workspaces. The sessions' working directories are different, but the sidebar history is global rather than scoped to the active workspace. This makes it easy to resume the wrong conversation.
A per-workspace/project filter by default, with an optional “all workspaces” view, would be very helpful.