Skip to main content
Memories help your Agents remember useful facts and preferences across conversations. They belong to your account and are available across your Agents. Sharing a Project leaves your Memories private to your account.

​
Add and find Memories in the dashboard

Open Memories in the Clawdi dashboard:
  1. Choose Create memory.
  2. Enter concise content and select a category.
  3. Save it, then use search or a category filter to find it again.
Synthetic Memories organized by facts, preferences, patterns, decisions, and context Concise records make durable context easier to review and recall over time. Open a Memory to inspect its source, creation time, and recall count when that information is available.

​
Check that your Agent can use it

Start a new conversation with an Agent that has working Clawdi tools. Ask it to recall the preference you saved. Use one clear fact per Memory, such as: “For project updates, start with a short summary and the next actions.” Keep passwords and API keys in Vaults. To remove outdated context, open the Memory and use its delete action. You can also ask your Agent to review and update a specific Memory.

​
Write a useful Memory

Keep one reusable fact, preference, pattern, decision, or piece of context in each Memory. Include the subject instead of relying on the current conversation.
Valid categories are fact, preference, pattern, decision, and context. If you omit --category, the CLI uses fact.
The search returns the new Memory. A supported Agent with working Clawdi tools can recall it in later conversations.
Never store passwords, API keys, private keys, tokens, or connection strings as Memories. Clawdi blocks likely secrets at this boundary; store them in a Vault instead.

​
Extract Memories from a Session

First make sure the supported Session is synced, then identify its local Session ID:
Extraction asks the service’s configured model to create Memories from that Session. Some deployments do not configure a memory-extraction model; in that case the CLI reports that extraction is unavailable and makes no Memories.Review extracted Memories in the dashboard and delete anything too broad, duplicated, sensitive, or no longer accurate.

​
Update an existing Memory

Use the full ID from JSON output to replace one Memory’s content:
This changes the chosen record’s content while keeping its category and source metadata. It does not create a new Memory if the ID is missing. Check the result before relying on it in a new Agent conversation.You can also ask an Agent with the appropriate Clawdi tools to review and update a specific Memory. Identify the exact record when several match, and keep secrets in Vaults.

​
Delete outdated context

The shortest path is the delete action on the Memory card or detail page. For the CLI, obtain the full ID from JSON output and remove that exact record:
Deletion removes the Memory from future recall. Use memory update when the same fact or preference has changed and you want to retain the existing record’s context. Delete it when it should no longer be remembered.If an Agent cannot recall a known Memory, verify its Clawdi tools with Connectors and MCP and see the MCP troubleshooting steps. Run clawdi memory --help for the command surface shipped with your CLI.
Last modified on September 10, 2026