Overview
Organize products into projects with files and instructions that guide the agent.
A project is a container that groups related chats, files, and instructions around a specific topic, product, or workflow. Projects let you build a focused knowledge base: the agent in any project chat automatically draws on project files and follows project instructions without you needing to repeat context each time.
What a project contains
- Chats: Conversations scoped to the project. Each chat inherits the project's files and instructions.
- Files: Uploaded documents (spreadsheets, reports, PDFs) that serve as automatic context for all project chats. See Project files.
- Instructions: Persistent guidance that shapes the agent's behavior across all project chats. See Project instructions.
Project hierarchy
You can nest projects as sub-projects to organize complex work. For example, a "Product Line Assessment" project might contain sub-projects for individual products, each with its own files and instructions.
Child projects inherit context from their parents: files uploaded to a parent project are available for retrieval in all child project chats, and instructions set at a parent level apply to all child projects. This lets you share common reference data and conventions across related workstreams.
When to use a project
| Scenario | Use |
|---|---|
| Quick one-off question | Standalone chat |
| Ongoing work on a specific product or topic | Project |
| Multiple analyses that share the same supplier data | Project with shared files |
| Different team members working on related analyses | Project with shared instructions |
Start with a standalone chat for ad-hoc questions. When a conversation evolves into sustained work, move it into a project to gain access to persistent files and instructions.