Adding on to here, have the same issue. Created a project today, added python .py files, asked questions that could be answered clearly with those files, and even directly asked GPT to open, read analyze and answer questions about the files I uploaded. Nothing worked, it is as if I opened a chat outside of the Projects context - I don’t understand how the most basic feature stops working like this!
I am using GPT Team tier.
Okay, for me, I was being stupid. Google updated something I think, which made it so that uploading a file with multiple tabs would only upload one tab, unless you did it from the drive, rather than the document. That solved it for me.
Having a similar problem on pro tier. When I upload a file, it shows the project files window displaying a file named “index.qmd” with a message indicating its contents may not be accessible.
This is what the o1 model says to me when i ask it why it can’t see my project file:
I wasn’t sure how to submit this, but this looks like the place, but it looks like it. I used the a.i. to help me a bit with the wording and format.
Bug Report / Diagnostic Memo
Title:
Project File Mismanagement Due to Improper File Handling: Move vs. Copy Error
Summary:
During structured project workflows, when a request by the user issues a instruction, other than to “copy” files from the ChatGPT Teams project folder, the default command used by the assistant is to “move” the files. The STATUS of the ChatGPT Teams project folder is the files have been “moved” and no longer exist in the source folder.
In the case of a “reset”, the files are removed locally, and the files are marked ‘expired’. When the assistant attempts to access the file, and “expired file” error is returned to the assistant. The folder appears to contain the file but can’t access a file marked as ‘expired’.
This led the assistant to interpret the files as inaccessible and then prompts user to re-upload the files, despite the files remaining in the persistent project directory. This caused redundant user effort to recreate progress that had seemingly vanished.
Technical Details:
| Aspect | Description |
|---|---|
| Context | Project-based session using structured file staging: Source → Extracted → Analyzed |
| User Instruction | “Extract all files in the project… move the files from the zip file to the folder…” |
| System Behavior | Interpreted instruction as move from project folder, instead of copy |
| Observed Consequence | Files disappeared from assistant’s accessible memory; appeared as missing or expired |
| Additional Symptom | Files marked “expired” even though they were stored in the persistent project directory |
Root Issue:
By default, the system moves files from the project folder during certain operations (e.g., ZIP extraction or file handling), instead of copying them. This violates the user’s intent that the project folder act as a read-only, permanent source of truth. The assistant misinterprets file presence due to internal access limitations, incorrectly flagging files as missing or expired. This disconnect has caused session regressions, user confusion, and redundant work.
Proposed Fixes:
Make Project Folder Immutable
Override Defaults
Display Warning or Confirmation
Clarify Expired Status
Session Continuity Improvements
Conclusion:
This bug has resulted in misinterpretation of persistent project data, causing assistant sessions to lose access to critical files. It has led the user to mistakenly initiate recovery work, duplicate analysis steps, and consume additional system and cognitive resources. Ensuring consistent file visibility and correct access semantics will improve project continuity, restore trust in the assistant’s reliability, and minimize unnecessary user labor.
