Collections
Collections are organizational containers for your memories - like projects or workspaces.Collections are manual organizational units. You control what goes where.
Why Use Collections?
- Separate contexts: Keep work, personal, and project memories distinct
- Targeted search: Search only within relevant collections
- Access control: Different API keys can have different collection permissions
- Multi-tenancy: Isolate data for different users or customers
Creating Collections
Collection names are case-insensitive. “Work” and “work” are treated as duplicates.
Storing Memories in Collections
Always specifycollection_id when storing memories:
Searching Within Collections
Managing Collections
- List
- Get
- Update
- Delete
Common Patterns
| Pattern | When to Use |
|---|---|
| One collection per user | User-specific memory/context |
| One collection per project | Project-scoped documentation |
| One collection per data type | Different content types (docs, chats, notes) |
Best Practices
- Use descriptive names -
customer_supportnotcollection_1 - Leverage metadata - Store organizational info in collection metadata
- Specify collection_ids for targeted searches - Faster, scoped searches
- Plan for scale - Consider collection strategy early
Next Steps
- Memory Operations - Store and search memories
- Metadata Filtering - Advanced filtering