Codex context persistence issue after closing folders in VS Code
What version of the IDE extension are you using?
1.109.3
What subscription do you have?
free
Which IDE are you using?
vs code
What platform is your computer?
windows WIN11 64bit
What issue are you seeing?
I am experiencing an issue with Codex's context management. When I finish a session, close the current folder, and open a new project folder, Codex seems to remain "locked" to the previous environment.
If I return to an existing chat, Codex attempts to apply code changes or suggestions to the previously closed folder instead of the currently active one. It fails to recognize that the workspace has changed.
What steps can reproduce the bug?
Open Folder A and start a chat with Codex.
Close Folder A and open Folder B.
Return to the previous chat session.
Ask for a change; Codex tries to modify files from Folder A (the closed one).
What is the expected behavior?
Codex should dynamically update its context based on the currently open workspace or prevent modifications to closed directories.
Additional information
just, i love codex it's cursor killer❤️
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
We don't recommend using the same conversation in different projects. The context history will contain references to the original project, and the model will assume that it's working within that context.
The new Codex app prevents this entirely, and the Codex CLI makes it difficult to do without jumping through some hoops. We'll probably make a similar change to the IDE extension and filter the session history based on the current project.