Compare
Compare

Supermemory sends your chats to a hosted memory model. recall keeps them on your machine and searches them there.

Supermemory ingests what you send, runs its own model over it into a vector-graph store, and hands context back at runtime, with plugins for Claude Code, Cursor and Codex. recall reads the transcripts those agents already keep, indexes them with no model calls, and writes notes overnight with a model you choose.

Checked 17 Oct 2026recall 0.5.1Supermemory on GitHub ↗

01At a glance

Supermemory and recall both aim at coding agents and both have plugins for Claude Code, Cursor and Codex. Supermemory's plugins send your sessions to its cloud, where its own model turns them into memories you query over the network. recall never sends the sessions anywhere: it reads the transcript files on disk, indexes them with no model, and writes its notes with whichever model you point it at.

Table 1 · recall and SupermemoryThe short answers; the sections below take each in turn.
recallSupermemory
RunsOn your machineIts cloud; a closed-source self-host binary on the $399 plan
LicenceMITSDKs MIT; the server is not public
Model calls to store a chat0Its model at ingest, or your LLM when self-hosted
A search takes11 ms local, 47 with embeddings187 ms server-side, 356 ms end to end
PriceFree$5 of credits free; $19, $100, $399 a month; Enterprise
Chat text leaves your machineNo, with a local modelYes: to its cloud and model, unless self-hosted
Claude Code, Codex, CursorMCP, skill, session hookPlugins for Claude Code, Cursor, Codex; hosted MCP server

02Where both were measured

On SWE-ContextBench, the benchmark's authors found Supermemory put the past fix behind a new issue in its top fifteen 59.6% of the time, after 370k tokens of model calls to take in the 300 sessions. recall 0.5.1 finds it 97.0% at the same cutoff with no model calls, and 79.8% in its top five. The paper does not define its metric, so read the gap loosely.

On LongMemEval, Supermemory reports 85.2% with Gemini 3 Pro and 84.6% with GPT-5, judged by GPT-4o; recall 0.4.1 scores 88.4% with Claude Haiku 5.5 as both. Different models and judges, so the ranking is loose. recall's retrieval alone finds an answering session in the top five 98.7% of the time; Supermemory publishes no retrieval figure.

recall 0.5.1 and SupermemoryThe past fix on SWE-ContextBench, answers correct on LongMemEval, and the latency of a search.↑ Higher is better, except latency
Fig 1
97.0%of new bug reports have the past fix in recall's top 15
+37.4points over Supermemory on the same 300 sessions, with no model calls
Past fix in the top 15SWE-ContextBench
  • recall 0.5.197.0%
  • Supermemory59.6%
Answers correctLongMemEval_S
  • recall 0.4.188.4%
  • Supermemory · Gemini 3 Pro85.2%
  • Supermemory · GPT-584.6%
Search latency, medianone query↓ fewer
  • Supermemory · server187 ms
  • recall 0.4.1 · keywords11 ms
  • recall 0.4.1 · hybrid47 ms
SWE-ContextBench Lite, 99 issues, 300 sessions · LongMemEval_S, Supermemory's own runs · latency from its site and recall's laptop
Supermemory's SWE-ContextBench figure is the paper's run of a metric it does not define. Its LongMemEval runs were judged by GPT-4o; recall 0.4.1 used Claude Haiku 5.5 as answer model and judge. Its 97% figure with GPT-4o is labelled Recall@20 with aggregation, not an answer accuracy.

03Cost

Supermemory sells credits: $5 worth free each month, $20 on the $19 Pro plan, $130 on Max at $100, $600 on Scale at $399, the plan that also allows self-hosting. Each ingest spends credits on its model, and a coding agent's sessions are long.

recall costs nothing to index or search. The nightly notes cost what your model costs: nothing with a local one, nothing extra on a Claude or ChatGPT subscription, batch prices on an API key.

Table 2 · CostWhat storing and reading memory costs.
recallSupermemory
Model calls to store a chat0Its model at ingest, or your LLM when self-hosted
PriceFree$5 of credits free; $19, $100, $399 a month; Enterprise
To take in 300 sessions$0, no model calls370k tokens of model calls, under an hour
Cost of memoryOne nightly run, your modelCredits, spent at ingest

04Latency

Supermemory's site gives 187 ms server-side for a search and 356 ms end to end: the round trip to its cloud, with ingest in the background.

recall searches a local index: 11 ms at the median on ~2,800 real chats, 47 ms with the embedding model's ranking. The index updates when the agents write new chats, with nothing to wait for.

Table 3 · LatencyWhat an agent waits for.
recallSupermemory
A search takes11 ms local, 47 with embeddings187 ms server-side, 356 ms end to end
Wait at write timeNone: reads saved chatsBackground ingest and a second model pass

05Privacy

Supermemory's plugins forward your sessions to its cloud, where its model reads them; it claims SOC 2, a HIPAA BAA and GDPR, but does not say which region holds the data. The self-host build keeps data in an encrypted folder but comes as a binary from a non-public codebase, runs telemetry unless you switch it off, and still needs an LLM key.

recall is open source end to end and reads your chats read-only on your machine. It redacts secrets before indexing, sends no telemetry, and makes no network calls except to the model you chose for the nightly notes. With a local model, nothing leaves.

Table 4 · PrivacyWhere your chat text goes.
recallSupermemory
RunsOn your machineIts cloud; a closed-source self-host binary on the $399 plan
LicenceMITSDKs MIT; the server is not public
Chat text leaves your machineNo, with a local modelYes: to its cloud and model, unless self-hosted
ComplianceNothing to certify: no serviceSOC 2, HIPAA BAA, GDPR claimed; no region stated
TelemetryNoneOn by default in the self-host build

06How memory is built

Supermemory's memory is made by its model: content is chunked and embedded, then a second pass extracts facts, keeps a static and a recent-activity profile, handles contradictions and forgets, inside its temporal vector-graph engine. What it keeps is Supermemory's to show you through its API.

recall's memory is files. The index holds every chat whole; the notes are markdown in git, each with its type, its project and the chats it came from, written once a night and consolidated rule by rule. Notes written by Claude Haiku 5.5 hold 91% of the conventions a mentor set on MemoryCode, and loaded at session start they lift an agent from 32% to 75% on long histories.

Table 5 · How memory is builtWhat is kept, and in what shape.
recallSupermemory
Captured byReading the agents' own chat filesPlugins forwarding sessions, or your code
Memory isMarkdown notes in git, plus an index of every chatFacts and profiles in a vector-graph engine
RetrievalFull-text index, five rankings fused; optional local embeddingsVector, full text and graph, with a profile
You can edit itYes, and the edit winsThrough the API

07Which to pick

Pick Supermemory if

  • You want a hosted memory API for an application, with user profiles and a graph, and a plugin that also covers your coding agents.
  • You are happy for your sessions to be processed by a hosted model, and the credit plans fit.
  • You need compliance paperwork from a vendor rather than a tool on your own machine.

Pick recall if

  • You want your coding agents to remember without any session leaving your machine.
  • You want search with no model calls and millisecond latency, over everything the agents ever saved.
  • You want memory as readable markdown in git, written by a model you chose.

08Questions

Is Supermemory open source?

Its SDKs, tool wrappers and agent skills are MIT, but the server is built from a separate, non-public codebase, and the hosted memory model is Supermemory's own. recall's code is all MIT, and there is no server behind it.

Which found the past fix more often?

On SWE-ContextBench, Supermemory put the past fix in its top fifteen 59.6% of the time in the benchmark's paper. recall finds it 97.0% at the same cutoff and 79.8% in its top five, with no model calls. The paper does not define the metric, so compare loosely.

Can I self-host Supermemory for free?

Self-hosting is a feature of the $399 Scale plan, and the binary is free within a lite licence limit the docs do not state. You also bring your own LLM key. recall is free to run anywhere, and with a local model costs nothing at all.

Do both work with Claude Code, Cursor and Codex?

Yes. Supermemory installs a plugin in each that sends sessions to its cloud and queries it back. recall connects through an MCP server and a /recall skill, with a hook that loads your notes at session start; it reads the agents' own transcript files, so no plugin captures anything.

SourcesSupermemory on GitHub · github.com/supermemoryai/supermemorySupermemory: how it works · supermemory.ai/docs/concepts/how-it-worksSupermemory self-hosting and its configuration · supermemory.ai/docs/self-hostingSupermemory pricing · supermemory.ai/pricingSupermemory research: LongMemEval runs · supermemory.ai/research/longmembenchSWE-ContextBench, Zhu et al. · arxiv.org/abs/2602.08316recall's benchmarks and method · github.com/alirng/recall/blob/main/docs/benchmarks.md