How mem0ai/mem0 works
Mem0 is a memory layer for AI applications, delivered as Python/TypeScript SDKs, a self-hosted API and dashboard, command-line tools, and agent-framework integrations. The central workflow is to submit conversational content, extract and embed memories, store them, then retrieve relevant context for an agent. The graph preserves documented product branches and sampled internal layers; some subsystem wiring is based on README claims because their implementation was not sampled.
Main entry points: server/main.py API application · memory/main.py Memory engine · client/main.py SDK clients · factory.py Provider factory
Components 24
Memory SDK
- SDK clients
mem0/client/main.py - Memory engine
mem0/memory/main.py - Provider setup
mem0/memory/setup.py - Provider factory
mem0/utils/factory.py - LLM configuration
mem0/configs/llms/base.py - Memory prompts
mem0/configs/prompts.py - Result reranking
mem0/configs/rerankers/base.py - Memory storage
mem0/memory/storage.py - LLM providers
mem0/llms/openai.py - Embedding providers
mem0/embeddings - Vector stores
mem0/vector_stores
Self-hosted Service
- API application
server/main.py - Authentication
server/auth.py - API routes
server/routers - Service database
server/db.py - Service models
server/models.py - Management dashboard
server/dashboard/src/app/(root)/dashboard - Server telemetry
server/telemetry.py
Command-line Tools
- CLI commands
cli/python/src/mem0_cli/app.py - Platform backend
cli/python/src/mem0_cli/backend/platform.py
Agent Integrations
- Agent plugins
integrations/kimi-plugin/core/memory_core.py - OpenClaw integration
integrations/openclaw/index.ts - SDK integrations
integrations
Other components
- Developer or agent
Connections 27
- Developer or agent → SDK clients: submits content
README.md - SDK clients → Memory engine: uses local memory
mem0/__init__.py - SDK clients → API application: calls API
- Memory engine → Provider setup: initializes
mem0/memory/main.py - Memory engine → Provider factory: selects providers
mem0/memory/main.py - Provider factory → LLM configuration: builds providers
mem0/utils/factory.py - Memory engine → Memory prompts: uses prompts
mem0/memory/main.py - Memory engine → Memory storage: stores history
mem0/memory/main.py - Memory engine → Vector stores: uses vector store
mem0/memory/main.py - Memory engine → Result reranking: supports reranking
- Provider factory → LLM providers: constructs LLM
mem0/utils/factory.py - Provider setup → Embedding providers: configures embedder
- API application → Authentication: uses auth
server/main.py - API application → API routes: registers routes
server/main.py - API routes → Service database: uses database
server/routers/auth.py - API routes → Service models: uses models
server/routers/auth.py - Management dashboard → API application: manages service
- API application → Server telemetry: reports events
server/main.py - Developer or agent → CLI commands: runs commands
README.md - CLI commands → Platform backend: uses platform backend
cli/python/src/mem0_cli/app.py - Platform backend → API application: calls API
- Developer or agent → Agent plugins: uses agent plugin
README.md - Agent plugins → API application: sends and searches memories
- Developer or agent → OpenClaw integration: uses agent integration
README.md - OpenClaw integration → API application: recalls memories
- Developer or agent → SDK integrations: uses SDK integrations
README.md - SDK integrations → SDK clients: connects SDKs