Skip to content

Bug/UX] ChatGPT loses access to previously uploaded project files – no way to reconnect #1780

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
engsilas opened this issue Apr 19, 2025 · 0 comments

Comments

@engsilas
Copy link

🧠 Context

When working with project files in ChatGPT, users can upload .zip or other files to the "uploads" panel in a project and expect them to be reusable throughout the session. However, the model loses access to these files across executions – even in the same conversation, and even after confirming the file's presence earlier.


❌ Problem

The file appears in the sidebar and was already accessed and confirmed by the model (e.g. the model lists files or shows contents). Later, if the user asks:

"Please re-extract the .zip file I uploaded earlier"

The model responds:

"That file is not in the zip"

This is despite having previously confirmed it was.


🔍 Root cause (likely)

It seems the execution environment (sandbox) is ephemeral. When the environment resets, the model can no longer access previously extracted content or uploaded files – even though the project interface shows them.

There is no way for the user to reconnect a file to the model, and the model does not notify the user that access to the file was lost.


🧭 Expected behavior

  • Files uploaded to a project should be accessible across executions.
  • The model should be able to reference them reliably via filename or ID.
  • At minimum, the user should be able to click "Reconnect this file to model" in the UI.
  • If the model cannot access a previously seen file, it should say:

    "I’ve lost access to the file – please reupload it."


✅ Recommendation

  • Add persistent access to project uploads
  • Provide a UI way to “reconnect” a file
  • Improve model feedback when a file is no longer accessible
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant