Features
Memory
Store useful information so InfuseOS can use it again later.
Memory
Memory helps InfuseOS remember useful context so you do not have to repeat the same background every time.
Screenshot
[IMAGE PLACEHOLDER: Memory save and search flow inside chat]
What Memory Is Good For
| Good for Memory | Not good for Memory |
|---|---|
| SOPs and repeat processes | One-time temporary notes |
| Team templates | Sensitive data you should not share |
| Product or client context that changes slowly | Random mixed notes with no title |
| Definitions, rules, and preferences | Generated outputs that belong in Library |
Personal vs Workspace Memory
| Scope | Who can use it | Use it when |
|---|---|---|
| Personal | Only you | It is your private working context |
| Workspace | Team members in the workspace | The team needs shared context and consistency |
How to Save Better Memory
Save one topic at a time
Avoid mixing unrelated subjects in one entry.
Use clear titles
Include team, topic, version, or date when helpful.
Choose the correct scope
Personal and workspace memory should be kept intentional.
Naming Format That Works
[Team or Area] - [Topic] - [Version or Date]Examples:
Sales - Onboarding SOP - v3Support - Escalation Rules - CurrentProduct - Release Checklist - 2026-03
Memory vs Library
| If you want to... | Use |
|---|---|
| Save instructions or knowledge for later reuse | Memory |
| Save a generated file or result | Library |
Retrieval Prompt Examples
Find our latest onboarding checklist in workspace memory and summarize it in 8 bullets.Search memory for our escalation policy and list only the response-time rules.Compare the current release checklist in memory with the previous version and show the key differences.Common Mistakes
- Saving content with names like "Notes" or "Final".
- Putting personal data into workspace memory.
- Keeping outdated versions without labels.
Memory works best when entries are specific, labeled clearly, and saved with the right scope.