ChatGPT Work receives only 16 of 28 Project Sources; regular Chat can access all files
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)?
26.908.70816
What subscription do you have?
Pro
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
ChatGPT Work receives only 16 of 28 Project Sources; regular Chat can access an omitted file
I am experiencing a reproducible file-access discrepancy in my project, observed September 15–16, 2026.
The Project Sources panel contains 28 files. My existing Work conversation receives only 16, matching the oldest 16 entries in the source list. The 12 newer entries are omitted from the project-source files supplied to that conversation.
One omitted file exists in Project Sources and opens successfully in the browser as a 17-page PDF. Two September 15 meeting-minutes compilations are also omitted from Work’s supplied source set, although both open in the Project Sources preview.
I tested the following within the same project:
The existing Work conversation could access only the 16 supplied project-source files.
A separate regular Chat conversation could access the schedule without issue.
A newly created Work conversation also reported seeing only 16 files.
Starting a new Work conversation therefore did not resolve the discrepancy. The technical cause remains unknown; these results do not establish a general 16-file limit.
This creates a significant quality risk. I use the project sources for engineering, scheduling, permitting, and meeting-record reviews. Work produced reviews without recognizing that newer sources were missing, creating the risk of conclusions based on outdated or incomplete information.
Please investigate the difference between regular Chat and Work’s access to this project’s sources, identify the cause, and restore reliable access to the existing files and subsequent additions without requiring duplicate uploads. The resolution should verify actual content access, not merely filename visibility, and clearly disclose any sources that remain inaccessible.
What steps can reproduce the bug?
Feedback ID: no-active-thread-01a0aa36-f983-7d43-ad1d-d5c392cdc97b
What is the expected behavior?
I expect both Chat and Work to be able to access all Project Source files.
Additional information
No response
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
Start with Feedback ID no-active-thread-01a0aa36-f983-7d43-ad1d-d5c392cdc97b and compare source access in the existing and new Work conversations with regular Chat. Done means identifying why 12 of 28 Project Sources are omitted, restoring access to all files, and verifying actual content access rather than filenames alone.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100