Codex creates a second project when it creates new threads
What version of the Codex App are you using (From “About Codex” dialog)?
26.730.61639, build 6234
What subscription do you have?
Pro
What platform is your computer?
Darwin 25.6.0 arm64 arm
What issue are you seeing?
I opened a thread in an existing pinned project. In that thread, I asked Codex to create one new thread for each issue. I wanted to work on each issue in a separate thread.
Codex created the threads. However, the threads did not appear in the existing pinned project. The Activity view showed the threads in a second project. The second project was not pinned. Both projects used the same local folder.
Example:
- Existing pinned project: Website Redesign
- Local folder:
/path/to/website-redesign - Result: Codex created or used a second project for the same folder.
- The new threads appeared in the second project.
The threads were not lost. Codex assigned them to the wrong project.
What steps can reproduce the bug?
- Open a thread in an existing pinned project.
- Ask Codex to create one new thread for each of several issues.
- Open the project in the sidebar.
- Open the Activity view.
Actual result: The new threads are not in the existing project. The Activity view shows them in a second, unpinned project for the same folder.
What is the expected behavior?
Codex must put the new threads in the project that contains the source thread.
Codex must not create or use a second project for the same local folder.
Additional information
All 14 new threads in this test had this problem.
Source session ID: 019fcef3-a1af-73b0-9b20-ff489eadc4f7
I reproduced this problem one time. I used Codex Desktop 26.730.61639, build 6234.
This problem is different from #23942. In this test, Codex assigned the threads to a second project record.