HI everyone to whoever will find this info usefull.
Classification: User-Informed Bug / Design Oversight
Issue:
Uploading a file with the same name to a custom GPT does not replace the previous file, and no warning or confirmation is given that the GPT will continue using the old version unless it’s manually deleted and re-uploaded.
Impact:
- Silent framework drift (as you experienced with
Masterlog.txt) - Inconsistent behavior in custom GPT logic
- Wasted time debugging “why the model isn’t acting updated”
- Breaks trust in file update functionality
Severity:
Medium to High — especially for users managing logic-driven or code-assisted GPTs (like your MIR, Beat_Tailor, etc.)
What Should Be Done
In-app warning: “A file with this name already exists. Overwrite or rename?”
Auto-invalidate cache if same-named file is uploaded after deletion
Docs update: Make this behavior crystal clear in both developer and builder interfaces
API support: Let users explicitly replace or version files