[Windows][App][Projects] False “files could not be synced” warning when project sources are available
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.810.52044 — released 15 Aug 2026
What subscription do you have?
ChatGPT Plus
What platform is your computer?
Microsoft Windows 11 x64
What issue are you seeing?
When I create a new Chat-mode conversation inside a ChatGPT Project, the app displays a warning stating that every project-source file could not be synced.
However, the supposedly unsynced files subsequently appear in the new chat’s available project context and can be accessed normally. The warning therefore appears to report a failed project-source handoff even though the handoff succeeds.
The warning count follows the exact number of project sources: it reported two unsynced files when the project contained two sources, then three unsynced files immediately after a third source was added.
What steps can reproduce the bug?
Feedback ID: no-active-thread-01a00fc4-754b-7952-b6fe-80f886c8c245
What is the expected behavior?
When a new Chat-mode conversation opens inside a Project, its project sources should be made available without a false synchronization warning.
If any source genuinely fails to sync, the warning should identify only the affected file or files and those files should actually be unavailable to the conversation.
Additional information
This has been reproduced repeatedly.
The warning changed from “2 files could not be synced” to “3 files could not be synced” immediately after a third project source was added. Despite both warnings, the complete set of sources was subsequently supplied to the new chat.
No file corruption or actual loss of source access has been observed. The practical problem is that the warning makes it impossible for the user to know whether a new conversation has received complete project context.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names no source file, test, or code entry point; begin with the Windows Project-to-Chat source handoff described in the issue and the supplied feedback ID. Done means reproducing the false warning, identifying why its count differs from actual availability, and confirming that warnings only name sources that are genuinely unavailable.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100