Menu
Stores a memory verbatim from user input with appropriate category classification. Use when the user says remember this, save this, store this, note that, or explicitly asks to record a preference, decision, goal, or lesson.
| name | remember |
| description | Stores a memory verbatim from user input with appropriate category classification. Use when the user says remember this, save this, store this, note that, or explicitly asks to record a preference, decision, goal, or lesson. |
Store a fact, preference, or learning directly into Mem0.
The user provides the content as an argument: /mem0-remember <text>
If no text was provided, ask: "What should I remember?"
Based on the content, pick the best category:
| Content signal | Category |
|---|---|
| "I prefer...", "I like...", "use X instead of Y" | preferences |
| "we decided...", "always use...", "never..." | decisions |
| "I learned...", "figured out...", "don't try..." | lessons |
| "my goal is...", "I want to...", "working toward..." | goals |
| "I work at...", "my role is...", "my team..." | work |
| "every day I...", "my workflow is..." | routines |
| "I'm working on...", "the project involves..." | projects |
| "John is...", "my manager...", "the team..." | relationships |
| "my name is...", "I'm from...", "I studied..." | identity |
| setup, tools, config, environment | technical |
| anything else | lessons |
Use the mem0_memory tool with:
action="add"content="<the user's text>"The /mem0-remember command stores verbatim — no inference. This is already handled by the command.
Remembered as <category>: "<content, first 80 chars>"
Append ... only if content was truncated (longer than 80 chars).
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local `Memory` class) to the mem0 Platform / hosted / managed SDK (the `MemoryClient` class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g. "migrate my mem0 setup to the platform", "switch from self-hosted mem0 to MemoryClient", "use my mem0 API key instead of a local Qdrant", "move mem0 to the cloud/hosted/managed service", or "replace my local mem0 vector store + embedder config with the platform". Applies to Python (`from mem0 import Memory` → `from mem0 import MemoryClient`) and TypeScript/JavaScript (`import { Memory } from "mem0ai/oss"` → `import MemoryClient from "mem0ai"`). Trigger even when the user doesn't say the word "migrate" but clearly wants their existing mem0 integration to run against the hosted platform. It first produces a reviewable migration plan, then executes it after the developer approves. Strictly scoped to th
Searches and injects relevant memories into context before starting work on a task or topic. Use when beginning a new task, switching context, or when past decisions, preferences, or knowledge need to be loaded.
Consolidates stored memories by merging duplicates, resolving contradictions, and pruning stale entries. Use when memory count is high, search results feel noisy or repetitive, or periodic cleanup is needed to maintain memory quality.
Deletes memories by search query or memory ID with confirmation before removal. Use when removing outdated information, incorrect memories, sensitive data, or cleaning up after experiments.
Pins or unpins a memory to protect it from pruning during dream consolidation. Use when a memory is critical and must never be removed, such as core preferences, important decisions, or immutable personal facts.
Searches memories and displays compact one-liner results, or looks up a specific memory by ID. Use for quick memory lookups, checking if something was recorded, resolving [mem0:id] citations, or browsing memories without full category detail.