What version of the Codex App are you using (From “About Codex” dialog)?
26.715.61943 (released July 21, 2026)
What subscription do you have?
ChatGPT Plus
What platform is your computer?
Microsoft Windows NT 10.0.22631.0 x64
What issue are you seeing?
When I try to create a Work chat inside an existing ChatGPT Project, I immediately receive errors such as:
- "Could not sync ChatGPT project context"
- "Could not use this project for a local chat"
The Work chat is not created.
What steps can reproduce the bug?
Feedback ID: 019f83d4-3c04-78a2-a4ce-3f1ff9273b23
What is the expected behavior?
A Work chat should be created inside the existing ChatGPT Project and retain access to the selected local folder. A Project should be able to contain one or more Work chats with access to local development folders.
Additional information
The problem occurs only when creating a local Work chat inside an existing Project.
Environment:
- Windows Desktop App
- ChatGPT Plus account
- Codex App version 26.715.61943
- Codex extension in VS Code works correctly
- Local folder access works outside Projects
Could you please confirm whether this is a known issue or a bug? Screenshots showing the error can be attached.
What version of the Codex App are you using (From “About Codex” dialog)?
26.715.61943 (released July 21, 2026)
What subscription do you have?
ChatGPT Plus
What platform is your computer?
Microsoft Windows NT 10.0.22631.0 x64
What issue are you seeing?
When I try to create a Work chat inside an existing ChatGPT Project, I immediately receive errors such as:
The Work chat is not created.
What steps can reproduce the bug?
Feedback ID: 019f83d4-3c04-78a2-a4ce-3f1ff9273b23
What is the expected behavior?
A Work chat should be created inside the existing ChatGPT Project and retain access to the selected local folder. A Project should be able to contain one or more Work chats with access to local development folders.
Additional information
The problem occurs only when creating a local Work chat inside an existing Project.
Environment:
Could you please confirm whether this is a known issue or a bug? Screenshots showing the error can be attached.