OpenAI Codex VS Code extension starts new chats in the wrong project folder
Mario34 · ghdev · 2026-07-21
A VS Code user reports that new Codex chats are being created in an old project instead of the folder currently open in the active window.
Symptoms
- cwd and writable root point to a stale workspace, e.g. /Users/<user>/Work/monorepo-app
- asking Codex to run pwd returns the wrong project path
- the extension appears to be reading selected-project from global user storage rather than the active VS Code workspace
Why it matters
The report warns this could be unsafe: commands, reads, and edits may run against a repository different from the one visibly open in VS Code.
Reproduction
- Open multiple VS Code windows with different folders
- Use Codex in one project
- Switch to another window
- Start a new chat
- The new thread still targets the old workspace
More from coding & agent
- Resin lets an agent build standalone LLM inference engines; vLLM and SGLang optimize DeepSeek kernels differently — AccBalanced · 2026-10-27
- Context layout is a cost decision: one memory edit can bust your entire agent prompt cache — dscape · 2026-10-27
- Alchemy adds effect/Workflow support across Durable Objects, Workflows and Lambda Durable Functions — samgoodwin89 · 2026-10-27
- Alchemy's Lambda Web Functions run plain Node web servers on Lambda, no OpenNext needed — samgoodwin89 · 2026-10-27
- Alchemy Domain brings domain-driven design and story testing to Effect backends — samgoodwin89 · 2026-10-27
- Alchemy makes all ~2,850 AWS bindings work from any cloud, not just S3/Lambda/DynamoDB — samgoodwin89 · 2026-10-27