Memory for Claude Code
Your agent finally remembers.
Persistent, local-first memory for Claude Code — living in your own Obsidian vault. Free, open-source, and it never leaves your machine.
Persistent, local-first memory for Claude Code — living in your own Obsidian vault. Free, open-source, and it never leaves your machine.
Your AI coding agent forgets everything between sessions. The usual fix is a hosted service that stores your context on their servers, for a monthly fee, in a format you can't read. Continuum does it with plain Markdown you already own.
| Continuum | Hosted memory SaaS | |
|---|---|---|
| Where your data lives | Your disk, your vault | Their servers |
| Cost | Free · MIT | $/month, per seat |
| Works offline | ✓ | ✗ |
| Open source | ✓ | usually ✗ |
| Format | Markdown + [[wikilinks]] | proprietary vector store |
| Telemetry | None | varies |
| Lock-in | None — keep your notes | export, maybe |
A handful of Claude Code hooks over a folder of Markdown notes. No server, no database, no network calls.
A session hook injects your durable briefing plus recent, project-aware activity — so a new chat starts already caught up.
Just-in-time retrieval matches your prompt to the vault and surfaces only the few relevant notes. Deduped, silent when nothing fits.
Every exchange is journaled; research and learnings get promoted into permanent, linked atomic notes.
The /obsidian skill distills the journal into curated, de-duplicated notes — newest fact wins, nothing is ever deleted, everything auditable in git.
Every hook is timeout-bounded, writes atomically, degrades to a no-op if the vault is gone, and logs failures. /obsidian doctor self-tests it all.