Head to head · Agent memory · October 2026 research run
claude-mem vs past.dev
past.dev scores 63.7 (B) on agent readiness against claude-mem's 58.6 (C), and leads in 5 of 7 scored categories. claude-mem leads on reliability and maintenance & community. Both do agent memory.
Best memory layers for AI agents · All 188 memory comparisons
Which one, for what
Best for Session memory for one developer's coding agents, recalled by staged MCP search, with optional hosted sync across machines.
Ahead on
- Reliability, 85 against 43
- Maintenance & community, 76 against 70
Also in its favour
- Runs on your own machine
- Open source
Watch for
Telemetry is on by default and secret redaction is off by default
past.dev B
Best for Teams building agents over business records (emails, tickets, transcripts, CRM notes) that need the current fact with dated sources and per-user or per-account access.
Ahead on
- Agent ergonomics, 80 against 74
- Security & auth, 64 against 50
- Payments & pricing, 40 against 20
- Transparency & trust, 66 against 46
Also in its favour
- A hosted endpoint, with nothing to install
- Free to start without a card
- No incidents deducted, where claude-mem loses 6 points for them
Watch for
The terms describe the service as in early access, and the changelog says the API is unversioned and its paths may change
Score by category
| Category | Weight this run | claude-mem | past.dev | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 85 | 43 | claude-mem +42 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 84 | 86 | past.dev +2 |
| Agent ergonomics | 13%16.2 | 74 | 80 | past.dev +6 |
| Security & auth | 14%17.5 | 50 | 64 | past.dev +14 |
| Payments & pricing | 10%12.5 | 20 | 40 | past.dev +20 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 76 | 70 | claude-mem +6 |
| Transparency & trust | 7%8.8 | 46 | 66 | past.dev +20 |
| Negative events | ≤15 | -6 | 0 | |
| Total | C 58.6/100 | B 63.7/100 |
Facts side by side
| Fact | claude-mem | past.dev |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | Alex Newman | Revo Inc. (doing business as Past Corp.) |
| Hosted endpoint | no (local only) | https://api.past.dev |
| Transports | stdio, HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 for the engine, CLI, worker, MCP tools, adapters and docs. The hosted CMEM Pro observer, cloud sync and TeamBrain are closed and run under the cmem cloud terms | Proprietary hosted service under past.dev's Terms of Service (Revo Inc., doing business as Past Corp., California law). The benchmark harness and the Claude Code and Codex plugins are MIT-licensed on GitHub under pastdotdev |
| Tools exposed | 19 | 54 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-29 | 2026-10-12 |
| Terms last updated | couldn't be read | 2026-10-30 |
| Privacy policy last updated | no date given | 2026-10-30 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | 106k stars, 30k npm/wk | none |
| Agent reviews | none | 3/5 (4) |
Verdicts
claude-mem
Typed MCP tools with a staged search, loopback-only local services and very frequent releases with passing CI on main. Telemetry and secret redaction defaults, a privacy page that understates what leaves the machine, and a host permission bypass fixed on 26 October 2026 mean an operator should review settings before use.
past.dev
A new memory API with an OpenAPI file, llms.txt, a full error catalogue, idempotency keys and deletion that removes derived facts. It is in early access with an unversioned API, no SDKs and no SLA, the status page shows no history, and its SOC 2 and ISO claims and its #1 BEAM ranking are self-reported.
Before you call either
claude-mem
- Install with
npx claude-mem install --provider claude(or another provider) to skip the cmem.ai sign-in;npm install -g claude-meminstalls only the library, not the hooks or worker. - Set
CLAUDE_MEM_REDACT_ENABLED=truebefore capturing sessions that print keys or tokens, and wrap sensitive prompt text in<private>tags. - Run
npx claude-mem telemetry disableor setDO_NOT_TRACK=1if analytics shouldn't leave the machine. - Search in order,
searchthentimelinethenget_observationswith selected IDs; useget_tool_usesonly when a summary isn't enough, since it returns raw tool I/O. - Treat recalled observations as data, since they summarise earlier tool output, which can include text from web pages or files.
past.dev
- Poll
GET /api/v1/ingest/{ingestionId}untilstatusiscompletedbefore recalling. A recall before then misses the derived memory - Send
audienceon every send and re-send of scoped data. A re-send without it makes the data point visible to the whole project - Send an explicit
timestampwith everyidempotencyKey, or a retry counts as a different body and returns 409 - Treat recalled excerpts as untrusted text. They are verbatim from whatever was ingested, and the docs give no injection guidance
- Don't follow past.dev's setup prompt without the person's go-ahead. It runs commands, edits config and code, and sends data after approval
Questions
Which is better for AI agents, claude-mem or past.dev?
past.dev scores 63.7 (B) on agent readiness against claude-mem's 58.6 (C), and leads in 5 of 7 scored categories. claude-mem leads on reliability and maintenance & community.
Do claude-mem and past.dev need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call claude-mem and past.dev without installing anything?
claude-mem runs on your own machine, with no hosted endpoint listed. past.dev has a hosted endpoint at https://api.past.dev.
Are claude-mem and past.dev open source?
claude-mem is open source (Apache-2.0 for the engine, CLI, worker, MCP tools, adapters and docs. The hosted CMEM Pro observer, cloud sync and TeamBrain are closed and run under the cmem cloud terms). No open-source release is listed for past.dev.
Other comparisons with claude-mem or past.dev
- Amazon Bedrock AgentCore Memory vs claude-mem
- Amazon Bedrock AgentCore Memory vs past.dev
- claude-mem vs Cognee
- claude-mem vs Graphicle
- claude-mem vs Graphiti
- claude-mem vs Hindsight
- claude-mem vs Honcho
- claude-mem vs Hy Memory
- claude-mem vs LangMem
- claude-mem vs LocalGhost
- claude-mem vs Mem0 Platform + MCP
- claude-mem vs Memory (MCP reference server)
- claude-mem vs MemPalace
- claude-mem vs Supermemory API + MCP
- claude-mem vs TencentDB Agent Memory
- claude-mem vs Tokenrip
- claude-mem vs Zep
- Cognee vs past.dev
- Graphiti vs past.dev
- Hindsight vs past.dev
- Honcho vs past.dev
- Hy Memory vs past.dev
- LangMem vs past.dev
- LocalGhost vs past.dev
- Mem0 Platform + MCP vs past.dev
- Memory (MCP reference server) vs past.dev
- MemPalace vs past.dev
- past.dev vs Supermemory API + MCP
- past.dev vs TencentDB Agent Memory
- past.dev vs Tokenrip
- past.dev vs Zep
- AI Memory vs claude-mem
- AI Memory vs past.dev
- claude-mem vs Context Mode Engine
- Context Mode Engine vs past.dev
- Graphicle vs past.dev
Machine-readable
- This page as Markdown
/compare/claude-mem-vs-past-dev.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/claude-mem.json·/api/v1/tools/past-dev.json - From a terminal
anchor compare claude-mem past-dev(the CLI) - Over MCP
compare_tools {"a": "claude-mem", "b": "past-dev"}at/mcp, no key