Codex Desktop on Windows creates new threads in the wrong workspace
Open 💬 3 comments Opened Mar 29, 2026 by GeorgL90
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of the Codex App are you using (From “About Codex” dialog)?
26.325.31654
What subscription do you have?
ChatGPT Business
What platform is your computer?
Windows 11
What issue are you seeing?
When I try to create a new thread in Project B, Codex Desktop instead creates the thread in my currently active workspace, Project A.
What steps can reproduce the bug?
Project B is already added as a workspace
It has no existing threads yet, or they are all archived
Creating a new thread defaults to Project A instead of Project B
What is the expected behavior?
If I select Project B, the new thread should be created there
At minimum, the app should let me explicitly choose the target workspace before thread creation
Environment:
Additional information
Codex Desktop on Windows
Workspaces involved: Project A, Project B
Impact:
I cannot start the first thread in a workspace that currently has no thread history
The app appears to fall back to the current workspace instead of the intended target
3 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
When you say that you "select project B", how are you doing that? By clicking on it in the left panel? There's no way to "select" a project in that panel.
The intended workflow is that you create a new thread, then select the project you want that thread to be associated with. It defaults to the last project that you associated a new thread with.
This is also reproducible in the Codex Desktop app on macOS.
Steps to reproduce
Actual behavior
The first thread is created as a projectless thread outside the selected project. In my latest reproduction, its workspace was under
~/Documents/Codex/2026-07-16/nrather than inside the newly created project.Expected behavior
The first thread created from a project should be bound to that project's root directory.
This reproduces every time a new project is created and its first thread is started. It can cause generated files or edits to land outside the intended project, so the UI's selected-project context and the thread's actual working directory diverge.