One memory for your AI — decisions, preferences, project
context — in a SQLite file on your machine. We couldn't
read it if we tried.
This is the product. The capsule, the receipt, and the conflict alert are real hook output.
Using an AI agent? forget's llms.txt has setup instructions for LLMs.
LongMemEval, the standard long-term-memory benchmark. Full 500-question set, GPT-4o reader for every system.
Knowledge-update questions — where memory products usually fail because stale facts survive: 92.3%
The oracle row is GPT-4o reading the full transcript — the ceiling for any memory system on this protocol. Mem0 and Zep as published; forget measured on the identical question set, with memory building and retrieval running entirely on-device. Methodology and raw runs →
Three surfaces the hooks put in front of you — real output, not concept art.
The capsule: your goal, next action, parallel work, and any claim that's gone stale.
About to act on a fact that was later corrected? Both versions, labeled, before you commit.
Config, rules, hooks, scope, and a live MCP round-trip — checked end to end.
One local server, one connect command. Your existing MCP setup is
preserved and backed up; disconnect reverses everything.
Decisions surface from your conversations and your git history. The observation gate keeps facts and forgets junk — nobody writes documentation.
A context capsule opens every session with your open work. Relevant memories are pushed mid-conversation — and a conflict alert shows both versions when a fact was later corrected.
Claude Code, Cursor, or Codex — the answer comes back with the commit or conversation that decided it. Sync arrives sealed E2EE · IN DESIGN
Your model provider already reads your prompts. There is no reason your memory layer should be a second reader.
A compounding one — and today it lives on other people's servers.
In February 2026, a US federal court ruled that a defendant's AI conversations were not protected — the provider's terms said data could be used for training and disclosed. What you tell an AI is, legally, what you told a company.
U.S. v. Heppner, S.D.N.Y. 2026Rewind promised local-first privacy, pivoted to the cloud, and was acquired — its users were migrated onto the acquirer's terms overnight. Every startup holding your memories is one term sheet away from being someone else's database.
Rewind → Limitless → Meta, 2025A model provider cannot end-to-end encrypt memory its own servers must read, and it will never port your memory to a competitor's tool. Native memory features are silos by design.
structural, not a roadmap gap| forget | Mem0 | Zep | Native memory | |
|---|---|---|---|---|
| LongMemEval, full 500 | 81.8% | 49.0% | 63.8% | unpublished |
| Where your memory lives | your machine, always | cloud (self-host option) | their cloud | provider servers |
| Trust label on every read | ✓ | — | — | — |
| Decision receipts from git | ✓ | — | — | — |
| Session hooks: capsule · push recall · conflict alerts | ✓ | — | — | — |
| Follows you across tools | Claude Code · Cursor · Codex | via MCP | via SDK | one vendor's silo |
| Open source | Apache-2.0 | ✓ | core only | — |
Competitor properties as publicly documented, July 2026. Corrections welcome — open an issue.
You're on the list. We'll write when sync ships. ✓
No spam — launch news only.
~/.forget —
storage, search, and memory building all run on your machine, offline
included. The 81.8% LongMemEval score was measured with building and
retrieval running 100% on-device, so local isn't a demo mode; it's the
configuration we benchmark. There is no account, no telemetry, and no
server of ours in the loop.npx forget-connect disconnect
restores your original configs from backups and removes the hooks — third-party
settings are preserved byte-for-byte. Then delete ~/.forget and
your memories are gone. No account to close, no export request, no retention
window. It's your file.Because memory that cannot be deleted is surveillance. Ours forgets on command.
Supersede, retire, delete — every fact in forget can be struck through, and the strikethrough keeps the history. The logo is not a joke about the product. It is the product.
Your users' memories are your liability. A memory layer you cryptographically cannot read can't leak and can't be compelled. We're taking design partners.
Talk to us