supermemory

Integrate persistent multi-tenant memory into AI agents using the Supermemory v3/v4 API.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/lurodrisilva/personal-skills --skill supermemory-lurodrisilva
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: supermemory
Source: https://github.com/lurodrisilva/personal-skills/tree/main/ai/supermemory
Command: npx skills add https://github.com/lurodrisilva/personal-skills --skill supermemory-lurodrisilva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI applications and agents lose context between sessions, forcing users to repeat themselves and preventing personalization. This Skill provides the architectural rules, API patterns, and integration playbooks needed to add persistent, tenant-isolated long-term memory to any LLM application using Supermemory (supermemory.ai), covering ingestion, retrieval, SDK wiring, self-hosting, and memory lifecycle management. ## Core Features & Use Cases - Ingestion & Data Modeling: Ingest documents, files, and conversations with deterministic containerTag scoping, customId deduplication with diff billing, and async dreaming controls for read-your-writes timing. - Retrieval & Memory Lifecycle: Query extracted facts, raw chunks, or both via /v4/search modes, use per-container profiles for low-latency stable facts, and manage versioned updates plus soft forgetting with forget-matching dry runs. - SDK & Framework Integration: Wire the TypeScript/Python SDKs and @supermemory/tools v2 wrappers into Vercel AI SDK, OpenAI, Mastra, Claude's memory tool, LangChain, CrewAI, and Microsoft Agent Framework, plus the hosted Memory MCP and self-hosted binary on localhost:6767. - Use Case: You are building a support chatbot that must remember each customer's preferences across sessions. Use this Skill to design a per-user containerTag scheme, wrap your model with withSupermemory in full mode, and verify the deployment with the read-only API and search probe scripts. ## Quick Start Ask the AI to add Supermemory persistent memory to your agent with a per-user containerTag, using the withSupermemory wrapper and scoped API keys.

Frequently Asked Questions about supermemory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add long-term memory to my AI agent with Supermemory?▼

Add long-term memory by ingesting content via POST /v3/documents or /v4/conversations with a deterministic containerTag and customId, then recall facts with POST /v4/search. For framework apps, wrap your model with withSupermemory from @supermemory/tools v2, which requires both containerTag and customId.

What is the difference between Supermemory searchMode memories, documents, and hybrid?▼

searchMode memories (the default) returns extracted atomic facts from the temporal memory graph, documents returns raw document chunks for RAG grounding, and hybrid returns both. Use /v3/search only for document/SuperRAG queries, never for memory recall.

Can I self-host Supermemory instead of using the cloud API?▼

Yes, run npx supermemory local to start an API-compatible server on localhost:6767 with local embeddings and bring-your-own LLM, including fully offline Ollama setups. Managed connectors, the hosted MCP, and proprietary extraction models remain cloud-only, and the free self-hosted tier caps around 10k documents.

Why does Supermemory search return nothing right after I write a document?▼

Writes are processed asynchronously, so default dynamic dreaming means new content is not immediately searchable. Use dreaming: "instant" at ingest time or poll the document status until it reaches done before searching in the same session.

How do I isolate memory between users or tenants in Supermemory?▼

Isolate tenants by passing a deterministic containerTag (for example user_123 or org:acme:user:jane) in the JSON body of every write and search call. The containerTag is the hard isolation boundary, while metadata and filters provide soft filtering within a container.

Supermemory vs Mem0 or Zep for agent memory, can I migrate?▼

Supermemory differs by producing three artifacts per document (chunks, graph memories, and profiles) with diff billing keyed on customId. Dedicated migration guides exist at /docs/migration/from-mem0 and /docs/migration/from-zep for moving existing memory stores.