ChatGPT Projects: live-updating project source documents

Feature request for ChatGPT Projects: live-updating project source documents I would like to suggest a feature for ChatGPT Projects where project source documents can stay automatically updated when the original files change. Right now, Projects are very useful because we can add files, context, instructions, and work across multiple chats. But in real project work, source documents are not static. Architecture documents, security baselines, migration plans, requirements, naming conventions, runbooks, and compliance documents change during the work. If ChatGPT continues using an older uploaded version, it can give outdated guidance while appearing confident. For ChatGPT Projects specifically, it would be very useful to support live-linked project sources with automatic refresh and change awareness. The feature could include: - Project source documents that can be linked to an original file instead of only uploaded as static copies. - Automatic re-indexing when the original document changes. - A visible freshness status for each source document, such as Current, Changed since last used, Deleted, Permission lost, or Version pinned. - A “what changed since last time” summary inside the Project. - Warnings when a previous answer may be outdated because the source document changed after the answer was generated. - Support for choosing how each source behaves: always use latest version, pin to a specific version, or ask before updating. - A project-level change log showing which sources changed and when. The main goal is to prevent ChatGPT Projects from working on stale context. This would be very valuable for engineering, IT, security, cloud migration, legal, compliance, product planning, and documentation-heavy projects. In these workflows, one outdated source document can lead to wrong decisions, wrong scripts, wrong architecture guidance, or compliance risk. For example, if a project has an architecture document or naming convention document attached, and that document changes during the week, ChatGPT should know that the source changed before continuing to help. It should either use the latest version or warn the user that previous context may no longer be valid. This would make ChatGPT Projects much safer and more reliable for serious long-running work. In short: ChatGPT Projects should not only store project context; they should understand when that context changes.