One memory for your AI — decisions, preferences, project
context — in a SQLite file on your machine. We couldn't
read it if we tried.
You're on the list. We'll write when sync ships. ✓
For the end-to-end encrypted sync beta. No spam — launch news only.
Using an AI agent? forget's llms.txt has setup instructions for LLMs.
why is the payment provider Paddle and not Stripe?
Here's what happens after npx forget-connect — with no behavior change asked of you.
One local server, one connect command. Your existing MCP setup is preserved and backed up.
Decisions surface from your conversations and your git history. The observation gate keeps facts and forgets junk — nobody writes documentation.
Claude Code, Cursor, or Codex — the answer comes back with the commit or conversation that decided it.
End-to-end encrypted, device keys, no passwords. The server — ours included — only ever holds ciphertext.
Everything lives in one ~/.forget SQLite file on your
machine. Search, extraction, everything — offline included.
Ask why did we choose X? — the answer links back to
the commit or conversation that decided it.
The same memory in Claude Code, Cursor, and Codex. Your context follows you, not the tool.
Your model provider already reads your prompts. There is no reason your memory layer should be a second reader.
Memory is not a chat log. It is a compounding profile of you — 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 gapYour 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