One AI works. Another takes notes.
While your agent ships, a second model sits in the back of the room writing everything down — categorized, causal, searchable. Nothing from a session is lost. Including the parts you forgot.
Each note lands in a taxonomy, so your agent can recall the right kind of context on demand. A progressive-disclosure session index ~800 tokens for 50 observations keeps recall cheap — up to 95% fewer tokens in our docs' worked example (18,000 → 970 tokens).
- BeforePicked Postgres over SQLite for write concurrency.
- CurrentAuth middleware now rejects expired tokens (bugfix).
- NextWire the rate limiter into the same middleware.
Three steps to memory that travels
No infrastructure, no YAML, nothing to babysit. Connect once and forget about it — it won’t.
Install claude-mem
Already running it? You’re set. It quietly builds an observations DB as you work.
Join the waitlist
Drop your email. We’ll confirm you’re in line and email your invitation.
Connect CMEM Cloud
Paste one URL into any agent. Your memory follows you to every machine you’ll ever own.
Memory that compounds
The claude-mem engine runs locally and gets smarter with every session you ship.
Automatic capture
A second model observes every session and writes notes out-of-band — no prompting, no slowdown.
Auto-categorization
Every observation lands in a taxonomy: decision, bugfix, feature, discovery, security.
Search three ways
Semantic, keyword, and timeline search over everything your agents have ever done.
Causality threading
Before/after links connect why a change happened to what came next — not just isolated facts.
Multi-project isolation
Each project keeps its own memory. Privacy stripping runs as notes are written, on local-first SQLite.
Smart-explore
Structural codebase exploration that is 6–12× cheaper than reading files in full.
Boring in all the right ways
Quiet, durable, and deeply uninterested in your attention. Exciting memory infrastructure is how you end up with neither.
Offline by default
A local copy that always works. We sync in the background the moment you’re online.
Private & revocable
One link, scoped to you. Rotate or revoke it anytime — instantly.
Reach it anywhere
Laptop, server, CI, a friend’s machine. Same memory, one URL.
Early access
Be first in line — invitations roll out daily.
Synced in under a second
Incremental sync keeps the cloud copy fresh without slowing you down.
Your DB, untouched
We mirror the claude-mem schema exactly. Nothing proprietary, nothing locked in.
11 skills, bundled in
Every install ships a kit of slash commands. Search memory, build brains, explore code, and orchestrate work — all from the agent you already use.
Search past sessions and observations
Build a queryable brain from corpora
Structural codebase exploration, 6–12× cheaper
Deep-learn a repo into memory
Research and write implementation plans
Orchestrate plan execution with subagents
Trace code paths and flows
Report what happened across sessions
Supervise a long-running agent task
Explain how claude-mem works
Bump versions and changelog
Build a brain from
your own work
Compile a focused corpus from your own sessions, docs, and observations — then ask it questions in plain language. Answers come back sourced, across multi-turn conversations, with a 1M-token context window behind them.
- Build a corpus from your sessions, docs, and observations
- Prime it once, then ask multi-turn questions
- Query across a 1M-token context window
- Rebuild as your work grows — your brain stays current
Your agent dreams while you work
While one AI builds, a second one watches — turning what just happened into durable memory, in real time.
- 14:02Located the video source file in src/lib/
- 14:05Refactored the sync thread into Motion.tsx
- 14:09Tests pass — committed as a120a9b
- 14:14Mapped the component layout pre-Phase 2
- Observations generated live as you work
- Before / after threading keeps cause and effect linked
- Watch it dream in the live viewer
- Session consolidated the moment you stop
RAG is how agents retrieve knowledge. RAD is how they remember experience.
Every app you use becomes a memory
Memory shouldn't stop at the terminal. cmem pulls in the conversations and transcripts where your real work happens.
Works where you work
If it speaks MCP, it remembers.
10 languages + custom grammars
Your memory,
one URL away
When your invitation arrives, you get a private MCP endpoint. Paste it into Claude, your editor, or any MCP-aware agent and your claude-mem history is right there — read and write, synced live. Like the agent never left.
- Scoped to your account, never shared
- Works with any MCP client
- Revoke and regenerate in one click
Free during early access
The engine is open source and free to install today. Cloud sync is $0 during early access — join the waitlist and start syncing the moment your invitation lands.
Questions, answered
What is claude-mem?
claude-mem is an open-source memory plugin for Claude Code and other AI agents. While one AI works, a second AI takes notes about what it does — building a searchable memory that persists across every session.
Is my data private?
Yes. claude-mem is local-first: your observations live in a SQLite database on your own machine, with privacy stripping applied as memory is generated. Cloud sync is strictly opt-in.
What's an MCP link?
An MCP link is a personal MCP server URL that gives any MCP client — Claude Code, Cursor, Codex CLI, and more — secure access to your memory from anywhere.
Does it slow my agent down?
No. Observation generation runs out-of-band, so it doesn't block your agent. Thanks to progressive disclosure, sessions actually get cheaper as your memory grows.
What is RAD?
RAG is how agents retrieve knowledge. RAD is how they remember experience. RAD — Retrieval-Augmented Dreaming — is our term for live observation generation that captures what happened while you work. Dreaming ships in claude-mem today; RAD as an open standard is on the way.
What does cloud cost?
$0 during early access. Get CMEM Cloud and start syncing your memory to the cloud while we're in early access.
