gleaming junco
It would be extremely valuable to support project-level file context: a persistent set of documents (e.g. codebases, policies, rules) that are indexed and automatically used as retrieval context for all conversations within a project, similar to project-scoped RAG. This would eliminate repetitive uploads and significantly improve consistency and correctness. This feature would align naturally with the existing Project/Folder UX by allowing each project to act as a scoped knowledge boundary.
Problem:
When working on complex, long-running projects (e.g. codebases, governance roles, policies), users must repeatedly upload the same documents or restate the same context across multiple conversations. This leads to inconsistency, friction, and higher cognitive load.
Example Use Cases:
- Governance project: rules, regulations, meeting minutes should be consistently available across all related conversations.
- Software project: a codebase or architectural documents should ground all discussions without re-uploading files per chat.
Proposed Solution:
Allow each Project/Folder to have a persistent set of uploaded documents that are indexed and automatically retrieved (RAG-style) for conversations within that project.
Benefits:
- Eliminates repetitive uploads
- Improves consistency and correctness
- Enables deeper, long-running project work
- Aligns naturally with existing Project/Folder UX
Key Constraint:
- Project-scoped context must be strictly isolated to prevent knowledge bleed across projects.
- Users should have clear visibility and control over which documents are included in a project’s context.