Stop re-explaining your project every session. Anamnesis gives your AI a persistent memory, so every conversation picks up exactly where the last one left off and you stop paying to re-send old context.
No credit card · Works with Claude (Cowork, Desktop, claude.ai, Claude Code), ChatGPT, Codex CLI, and Gemini CLI.
One connector URL. Three steps. Memory that compounds every session.
Paste one URL into your assistant: Claude (Claude Code, Cowork, Desktop, claude.ai), ChatGPT, Codex CLI, or Gemini CLI. Automatic, hands-off session capture runs in Claude Code. On Cowork, Claude Desktop, and claude.ai the connector is read only: it recalls your saved memory into every chat, and you add memories on demand.
Episodes compress into echoes, echoes crystallize into engrams. Your project knowledge compounds with every session.
Your assistant retrieves what bears on the task at hand instead of a wall of old text. Fast, cheap context.
A live dashboard shows tokens saved, sessions continued, and memory built — updating in real time as you work. Watch your context bill shrink.
Four layers, borrowed from how human memory actually works.
Named for Tulving's episodic memory framework and Semon's engram theory. The science is real.
We built Anamnesis on a single rule: the data that flows through it belongs to you, not to us, an ad network, or whatever model gets trained next year. Here's exactly what that means.
Not ours, not Anthropic's, not OpenAI's. Your conversations never become somebody's training data. That's the load-bearing promise.
There's no ad tier, no anonymized-aggregates tier, no data-partner tier. You pay a subscription, and that's the whole business model.
No Google Analytics. No Facebook pixel. No session-replay tools. The only cookie we set is the one that keeps you signed in.
Every user's memory is encrypted with a key derived from their own credentials. Every API key is stored in one registry, encrypted under one server master key. That key is a deployment secret, not on the data volume. A copy of the volume alone can't decrypt anyone's memory. The running server holds the master key and can decrypt every account. See the full cryptography →
API keys, session cookies, and memory payloads all travel over TLS 1.2 or 1.3. Cookies are HttpOnly, Secure, SameSite=Lax: the conservative defaults.
During a request, the keys that open your memory are recomputed from your API key, then discarded. Your API key is kept only in the encrypted registry. The master key that opens the registry lives in the server's environment, not on the disk with your data.
Your dashboard is built from an encrypted index of titles and structure. The body of a memory is decrypted only when you open that one item — the system lists what you have without reading what's in it.
Incoming memories are checked for prompt-injection attempts and contradictions before they're trusted. Adversarial text gets quarantined for review instead of quietly becoming part of what your AI believes.
Download everything as a plain JSON archive. No proprietary container, no vendor lock-in. If you leave, you take the whole corpus with you.
Live data goes on delete, and backups holding it expire within 5 days. No hidden tombstones.
Free during the beta. One URL, one session, and your projects stop starting from zero. Export or delete at any time, no strings.