Memory and Project Context
Maintain user and project memory and understand automatic capture, reflection, and cleanup.
Open: Settings → Memory.
Memory stores short facts worth reusing across conversations, such as writing preferences and project conventions. Put temporary instructions in chat and complete documents in project files.
Choose a scope
| Scope | Suitable content | Where it applies |
|---|---|---|
| User | Preferred language and stable working habits | Conversations configured to use user memory |
| Project | Terminology, conventions, and project background | Open the corresponding project or working directory first |
| Bot | A persistent assistant's own context | Manage it in that Bot's details |
Memory use also depends on assistant settings and agent support. External agents and agents inside mini apps do not necessarily read these memories.
Add your first memory
- Open Memory settings and enable long-term memory.
- Select User, or open a project and select Project for a project-specific convention.
- Add a key such as
writing_stylewith the value “Start with the conclusion, then provide numbered steps.” - Save and check that the entry appears in the intended scope.
- Start a new conversation using that scope and ask for a short explanation. Check whether the output follows the preference.
A successful save confirms storage. The current task, assistant instructions, and model also influence the response.
Automatic memory options
| Option | Purpose | When to use it |
|---|---|---|
| Long-term memory | Controls use of long-term memory | Enable for preferences across conversations |
| Automatic capture | Extracts and saves lasting information from conversations | Disable for manual management; review saved entries when enabled |
| Model reflection | Uses the current chat model for extraction, with a rules fallback | Enable for model-assisted analysis; it may consume model usage |
| Automatic cleanup | Consolidates older entries when configured conditions are met | Set the interval, session threshold, and entry limit for your workload |
Automatic capture can save directly without individual approval. If pending candidates appear, save or dismiss them individually.
Edit, delete, or pause
Edit or delete outdated entries in their original scope, then verify with a new task. Disabling memory or automatic capture does not erase saved entries; remove those separately.
In file view, check whether the file belongs to the user or current project before editing and saving. Use the entry list if you are unfamiliar with the file format.
Why was a memory ignored?
Check that memory is enabled, the entry is in the right scope, the current conversation has the intended project open, and the assistant allows that memory scope. Make the entry concise and current, then test in a new conversation. See Privacy & Local Data for data boundaries.