Find a file
sohamd22 8c35c1ecad review suggestions option for inferred memories (#1138)
### TL;DR

Adds a swipeable "Review suggestions" card to the dashboard that lets users approve or decline inferred memories surfaced by Nova.

### What changed?

- Added a `ReviewMemoriesCard` component that appears in the "Suggested for you" section of the dashboard (both desktop and mobile layouts). The card is hidden when there are no pending inferred memories, so it never renders empty chrome. While the modal is open, the displayed count is frozen so the trigger button doesn't tick down or disappear mid-session. Switching spaces closes the modal automatically.
- Added a `ReviewMemoriesModal` component that presents inferred memories as a swipeable card deck. Users can approve (swipe right / ✓), decline (swipe left / ✗), or skip each memory. The modal includes:
  - Drag-to-swipe with a full-card color wash (green for keep, red for decline) and verdict pills that intensify as the swipe threshold approaches
  - Keyboard support: `→` to approve, `←` to decline, `↓` or `Space` to skip, and `Cmd/Ctrl+Z` to undo
  - An undo button that steps back one card and reverts the server-side decision, using refs to avoid stale-state bugs during rapid interactions
  - A progress dot indicator showing position in the queue alongside a numeric counter
  - A "All caught up" completion state summarising how many memories were kept
  - Reduced-motion support via `useReducedMotion`
  - The card queue is snapshotted when the modal opens so cache updates from review mutations don't reshuffle the stack mid-session
- Added a `useInferredMemories` hook to fetch the pending review queue for a given container tag, and a `useReviewInferredMemory` mutation hook that calls the review endpoint. On success it removes the reviewed entry from the cached queue directly; on undo it invalidates the query to refetch the restored memory from the server.
- Registered two new API schema entries: `GET /container-tags/:containerTag/inferred` to fetch the pending queue and `POST /container-tags/:containerTag/inferred/:memoryId/review` to submit an approve, decline, or undo action.

### How to test?

1. Ensure there are inferred memories pending review for a container tag.
2. Open the dashboard — a "Review suggestions" card should appear in the "Suggested for you" section showing the count of pending memories.
3. Click the card to open the modal and swipe or use the buttons/keyboard to approve, decline, or skip memories.
4. Verify that approved and declined memories are removed from the queue after each decision and that the completion state appears once all cards are reviewed.
5. Use the undo button or `Cmd/Ctrl+Z` to step back through decisions and confirm the server-side state is reverted correctly.
6. Confirm the card does not render when there are zero pending inferred memories.
7. Switch spaces while the modal is open and confirm it closes without carrying state into the new space.

### Why make this change?

Nova infers memories on behalf of users but may not always be fully confident in them. This feature gives users a lightweight, low-friction way to review and curate those suggestions directly from the dashboard, improving the quality and trustworthiness of their memory store.
2026-07-04 20:57:33 +00:00
.github/workflows fix: auto publish actions (#872) 2026-04-21 17:37:15 +00:00
apps review suggestions option for inferred memories (#1138) 2026-07-04 20:57:33 +00:00
packages review suggestions option for inferred memories (#1138) 2026-07-04 20:57:33 +00:00
skills/supermemory docs: quote pip extras install examples (#1039) 2026-06-16 23:30:41 -07:00
.gitignore fix 2026-03-05 14:01:46 -08:00
biome.json chore(nova): ux improvments (#820) 2026-04-02 18:20:34 +00:00
bun.lock chore(web): remove unused @lobbyside/react integration (#1156) 2026-06-23 10:00:59 -07:00
CLAUDE.md feat: supermemory MCP 4.0 (#631) 2025-12-30 12:03:21 -08:00
CONTRIBUTING.md easier for contrbutors 2026-05-06 22:46:44 -07:00
LICENSE Update LICENSE 2025-08-16 20:01:44 -07:00
package.json easier for contrbutors 2026-05-06 22:46:44 -07:00
portless.json use portless 2026-05-06 22:42:34 -07:00
README.md docs(readme): add Supermemory local — self-hosted binary (#1089) 2026-06-10 09:48:26 -07:00
README.zh-CN.md docs: add Simplified Chinese README (#1026) 2026-06-03 14:34:59 +05:30
turbo.json easier for contrbutors 2026-05-06 22:46:44 -07:00

Supermemory

State-of-the-art memory and context engine for AI. And yes - you can use it as a company/personal brain.

Docs · Quickstart · Self-host · Dashboard · Discord

npm pypi docs

English · 简体中文


Supermemory is the memory and context layer for AI. #1 on LongMemEval, LoCoMo, and ConvoMem — the three major benchmarks for AI memory.

We are a research lab building the engine, plugins and tools around it.

Your AI forgets everything between conversations. Supermemory fixes that.

It automatically learns from conversations, extracts facts, builds user profiles, handles knowledge updates and contradictions, forgets expired information, and delivers the right context at the right time. Full RAG, connectors, file processing — the entire context stack, one system.

🧠 Memory Extracts facts from conversations. Handles temporal changes, contradictions, and automatic forgetting.
👤 User Profiles Auto-maintained user context — stable facts + recent activity. One call, ~50ms.
🔍 Hybrid Search RAG + Memory in a single query. Knowledge base docs and personalized context together.
🔌 Connectors Google Drive · Gmail · Notion · OneDrive · GitHub — auto-sync with real-time webhooks.
📄 Multi-modal Extractors PDFs, images (OCR), videos (transcription), code (AST-aware chunking). Upload and it works.

All of this is in our single memory structure and ontology.

image

Use Supermemory

🧑‍💻 I use AI tools

Build your own personal supermemory by using our app. Builds persistent memory graph across every conversation.

Your AI remembers your preferences, projects, past discussions — and gets smarter over time.

→ Jump to User setup

🔧 I'm building AI products

Add memory, RAG, user profiles, and connectors to your agents and apps with a single API.

No vector DB config. No embedding pipelines. No chunking strategies.

→ Jump to developer quickstart

🖥️ I want to run it myself

State-of-the-art memory, on your machine. One binary. Zero config. Bring any model — or run fully offline with Ollama.

curl -fsSL https://supermemory.ai/install | bash

→ Jump to Supermemory local


Give your AI memory

The Supermemory App, browser extension, plugins and MCP server gives any compatible AI assistant persistent memory. One install, and your AI remembers you.

The app

You can use supermemory without any code, by using our consumer-facing app for free.

Start at https://app.supermemory.ai

image

It also comes with an agent embedded inside, which we call Nova.

Supermemory Plugins

Supermemory comes built with Plugins for Claude Code, OpenCode, OpenClaw, and Hermes.

image

These plugins are implementations of the supermemory API, and they are open source!

You can find them here:

MCP - Quick install

npx -y install-mcp@latest https://mcp.supermemory.ai/mcp --client claude --oauth=yes

Replace claude with your client: cursor, windsurf, vscode, etc.

Read more about our MCP here - https://supermemory.ai/docs/supermemory-mcp/mcp

What your AI gets

Tool What it does
memory Save or forget information. Your AI calls this automatically when you share something worth remembering.
recall Search memories by query. Returns relevant memories + your user profile summary.
context Injects your full profile (preferences, recent activity) into the conversation at start. In Cursor and Claude Code, just type /context.

How it works

Once installed, Supermemory runs in the background:

  1. You talk to your AI normally. Share preferences, mention projects, discuss problems.
  2. Supermemory extracts and stores the important stuff. Facts, preferences, project context — not noise.
  3. Next conversation, your AI already knows you. It recalls what you're working on, how you like things, what you discussed before.

Memory is scoped with projects (container tags) so you can separate work and personal context, or organize by client, repo, or anything else.

Supported clients

Claude Desktop · Cursor · Windsurf · VS Code · Claude Code · OpenCode · OpenClaw · Hermes

The MCP server is open source — view the source.

Manual configuration

Add this to your MCP client config:

{
  "mcpServers": {
    "supermemory": {
      "url": "https://mcp.supermemory.ai/mcp"
    }
  }
}

Or use an API key instead of OAuth:

{
  "mcpServers": {
    "supermemory": {
      "url": "https://mcp.supermemory.ai/mcp",
      "headers": {
        "Authorization": "Bearer sm_your_api_key_here"
      }
    }
  }
}

Build with Supermemory (API)

If you're building AI agents or apps, Supermemory gives you the entire context stack through one API — memory, RAG, user profiles, connectors, and file processing.

Install

npm install supermemory    # or: pip install supermemory

Quickstart

import Supermemory from "supermemory";

const client = new Supermemory();

// Store a conversation
await client.add({
  content: "User loves TypeScript and prefers functional patterns",
  containerTag: "user_123",
});

// Get user profile + relevant memories in one call
const { profile, searchResults } = await client.profile({
  containerTag: "user_123",
  q: "What programming style does the user prefer?",
});

// profile.static  → ["Loves TypeScript", "Prefers functional patterns"]
// profile.dynamic → ["Working on API integration"]
// searchResults   → Relevant memories ranked by similarity
from supermemory import Supermemory

client = Supermemory()

client.add(
    content="User loves TypeScript and prefers functional patterns",
    container_tag="user_123"
)

result = client.profile(container_tag="user_123", q="programming style")

print(result.profile.static)   # Long-term facts
print(result.profile.dynamic)  # Recent context

Supermemory automatically extracts memories, builds user profiles, and returns relevant context. No embedding pipelines, no vector DB config, no chunking strategies.

Framework integrations

Drop-in wrappers for every major AI framework:

// Vercel AI SDK
import { withSupermemory } from "@supermemory/tools/ai-sdk";
const model = withSupermemory(openai("gpt-4o"), { containerTag: "user_123", customId: "conv-1" });

// Mastra
import { withSupermemory } from "@supermemory/tools/mastra";
const agent = new Agent(withSupermemory(config, "user-123", { mode: "full" }));

Vercel AI SDK · LangChain · LangGraph · OpenAI Agents SDK · Mastra · Agno · Claude Memory Tool · n8n

Search modes

// Hybrid (default) — RAG + Memory in one query
const results = await client.search.memories({
  q: "how do I deploy?",
  containerTag: "user_123",
  searchMode: "hybrid",
});
// Returns deployment docs (RAG) + user's deploy preferences (Memory)

// Memories only
const results = await client.search.memories({
  q: "user preferences",
  containerTag: "user_123",
  searchMode: "memories",
});

User profiles

Traditional memory relies on search — you need to know what to ask for. Supermemory automatically maintains a profile for every user:

const { profile } = await client.profile({ containerTag: "user_123" });

// profile.static  → ["Senior engineer at Acme", "Prefers dark mode", "Uses Vim"]
// profile.dynamic → ["Working on auth migration", "Debugging rate limits"]

One call. ~50ms. Inject into your system prompt and your agent instantly knows who it's talking to.

Connectors

Auto-sync external data into your knowledge base:

Google Drive · Gmail · Notion · OneDrive · GitHub · Web Crawler

Real-time webhooks. Documents automatically processed, chunked, and searchable.

API at a glance

Method Purpose
client.add() Store content — text, conversations, URLs, HTML
client.profile() User profile + optional search in one call
client.search.memories() Hybrid search across memories and documents
client.search.documents() Document search with metadata filters
client.documents.uploadFile() Upload PDFs, images, videos, code
client.documents.list() List and filter documents
client.settings.update() Configure memory extraction and chunking

Full API reference → supermemory.ai/docs


Supermemory local — run it yourself

State-of-the-art memory, on your machine. One binary. Zero config.

curl -fsSL https://supermemory.ai/install | bash
# or
npx supermemory local
supermemory-server

First boot sets up the embedded Supermemory graph engine, local embeddings, and your credentials, then prints an API key. The full Memory API — documents, memories, user profiles, hybrid search — runs against http://localhost:6767.

const client = new Supermemory({
  apiKey: "sm_...",
  baseURL: "http://localhost:6767", // that's the only change
});
  • Bring any model — OpenAI, Anthropic, Gemini, Groq, or any OpenAI-compatible endpoint. An interactive wizard walks you through it on first boot.
  • Fully offline if you want — point it at Ollama (gpt-oss:20b works great) and nothing leaves your machine.
  • Your data, one directory — everything lives in ./.supermemory, easy to back up or move.
  • Same API as the platform — prototype locally, ship on the hosted platform by changing baseURL.

Read the self-hosting docs — quickstart, configuration, and local vs. Enterprise.


Benchmarks

Supermemory is state of the art across all major AI memory benchmarks:

Benchmark What it measures Result
LongMemEval Long-term memory across sessions with knowledge updates 81.6% — #1
LoCoMo Fact recall across extended conversations (single-hop, multi-hop, temporal, adversarial) #1
ConvoMem Personalization and preference learning #1

We also built MemoryBench — an open-source framework for standardized, reproducible benchmarks of memory providers. Compare Supermemory, Mem0, Zep, and others head-to-head:

bun run src/index.ts run -p supermemory -b longmemeval -j gpt-4o -r my-run

Benchmarking your own memory solution

We provide an Agent skill for companies to benchmark their own context and memory solutions against supermemory.

npx skills add supermemoryai/memorybench

Simply run this and do /benchmark-context - Supermemory will automatically do the work for you!


How memory works under the hood

Your app / AI tool
        ↓
   Supermemory
        │
        ├── Memory Engine     Extracts facts, tracks updates, resolves contradictions,
        │                     auto-forgets expired info
        ├── User Profiles     Static facts + dynamic context built from engine, always fresh
        ├── Hybrid Search     RAG + Memory in one query
        ├── Connectors        Real-time sync from Google Drive, Gmail, Notion, GitHub...
        └── File Processing   PDFs, images, videos, code → searchable chunks

Memory is not RAG. RAG retrieves document chunks — stateless, same results for everyone. Memory extracts and tracks facts about users over time. It understands that "I just moved to SF" supersedes "I live in NYC." Supermemory runs both together by default, so you get knowledge base retrieval and personalized context in every query. Read more about this here - https://supermemory.ai/docs/concepts/memory-vs-rag

Automatic forgetting. Supermemory knows when memories become irrelevant. Temporary facts ("I have an exam tomorrow") expire after the date passes. Contradictions are resolved automatically. Noise never becomes permanent memory.



Give your AI a memory. It's about time..