Background
ChatGPT has evolved from a conversational assistant into a tool that many users rely on for long-term projects, including software development, research, writing, game development, and creative work.
Today, responses are generated primarily from:
- Shared long-term memory
- Current conversation history
- User-provided prompts and uploaded files
This works well for general conversations, but becomes increasingly difficult for large, long-lived projects.
The Current Problem
Long-term memory is shared across all projects.
When users switch between unrelated projects, memories from previous work may unintentionally influence responses.
To avoid this, users must repeatedly search through their own documents, retrieve the relevant information, and paste it into every new conversation.
Effectively, users become the retrieval layer in the RAG pipeline—acting as “organic RAG hardware.”
The issue is not the context window size.
The issue is that project knowledge exists, but ChatGPT cannot automatically retrieve it.
Existing Precedent
OpenAI has already demonstrated the value of project-aware retrieval through tools such as Codex.
Instead of relying solely on conversation history, these tools understand an entire project by retrieving only the files relevant to the current task.
This greatly improves long-term collaboration without requiring extremely large context windows.
Proposed Solution
Extend this idea beyond software development.
Allow every ChatGPT project to own a dedicated knowledge base backed by the user’s account storage.
Rather than treating uploaded files as temporary conversation context, ChatGPT could retrieve relevant project documents automatically before generating a response.
Possible knowledge sources include:
- Markdown
- Word documents
- Images
- Source code
- Notes
- Design documents
- Research papers
The retrieval process should be automatic and invisible to users.
Memory Architecture
Separate memory into two layers.
Global Memory
Personal preferences that apply everywhere.
Examples include:
- Preferred writing style
- Programming languages
- Favorite tools
- Communication preferences
Project Memory
Knowledge specific to one project.
Examples include:
- Character profiles
- Worldbuilding
- Technical specifications
- Research notes
- Project timelines
- Design documents
Project memories should remain isolated unless users explicitly choose to share them.
Benefits
This approach would:
- Eliminate repetitive copy-and-paste workflows
- Reduce prompt length
- Improve response consistency
- Keep unrelated projects isolated
- Better support large creative and engineering projects
- Reduce unnecessary context usage through targeted retrieval
Conclusion
ChatGPT is no longer just a chatbot.
For many users, it has become a long-term collaborator.
Project-scoped retrieval would build upon capabilities already demonstrated in OpenAI’s developer tools and make them available for every kind of project—not just software engineering.