Obsidian vs Claude Recall: stack-mates, not rivals
If you found this page searching “obsidian for claude code” or “obsidian claude memory plugin,” you are not actually choosing between the two. Obsidian indexes the notes you write. Claude Recall indexes the Claude Code sessions you already had. Different inputs. Different jobs. Both local-first. This page explains exactly when each is the right tool, and why most serious users end up running both.
TL;DR
- Obsidian is a Markdown-based knowledge graph for notes you write deliberately. The graph view, backlinks, and plugin ecosystem are its superpowers.
- Claude Recall is a memory layer for Claude Code that captures every session automatically — code reasoning, decisions, debugging traces — into a local SQLite database with full-text and semantic search.
- They share a value system: local-first, no cloud lock-in, your data on your disk. They do not overlap on inputs.
Side-by-side
| Capability | Obsidian | Claude Recall |
|---|---|---|
| Primary input | Markdown notes you write | Claude Code session JSONLs (auto-captured) |
| Local-first storage | Yes (plain Markdown on disk) | Yes (SQLite + plain-text mirror) |
| Knowledge graph view | Yes — its signature feature | Yes (cog-graph: skills, threads, sessions) |
| Captures Claude Code sessions automatically | Manual paste / plugin glue | Yes, zero-config |
| Full-text + semantic search | Full-text yes; semantic via plugins | Built-in, both modes |
| MCP server for AI agents | Via community plugin | Built-in |
| Best at | Curated knowledge you author | Recovering context from past coding sessions |
Why they are stack-mates
Obsidian gives you a vault of intentional notes: meeting summaries, design docs, research you wrote up. Claude Recall gives you a vault of unintentional knowledge: the three hours you spent debugging a flaky migration last March, the architecture decisions you talked through with the agent, the snippets you pasted into a long Claude Code session and forgot. Both are searchable. Both are yours. Together they cover the full surface area of what you actually know.
Where Obsidian wins
Obsidian is the right tool when the artifact is something you sat down to write. Meeting notes, daily journaling, project briefs, research notebooks, second-brain Zettelkasten systems. Its graph view, backlinks, and ten-year plugin ecosystem are unmatched for deliberately-authored knowledge. If you live in Markdown and want a tool that respects that forever, Obsidian is right.
Where Claude Recall wins
Claude Code sessions are the highest-density, lowest-effort knowledge artifact a developer produces today. You are reasoning about code, making decisions, narrating problems, getting answers. By default, Claude Code throws all of it away when the session ends. Claude Recall captures every session automatically into a local index you can search, link, and feed back to the agent on the next conversation. No paste-into-Obsidian discipline. No plugin glue. You did the work; the tool keeps the work.
The assembly burden
You can build something Claude-Recall-ish inside Obsidian with the right combination of plugins, scripts, hot-keys, and discipline. People do. The assembly takes weeks; the discipline lasts about three. Claude Recall ships that as defaults — a single install, automatic capture, daemon-managed indexing. You keep your Obsidian vault for the notes you write. You keep Claude Recall for the sessions you had.
The use case for each
- Use Obsidian when you want a vault of deliberately authored Markdown — notes, journals, project briefs — with backlinks and a graph view you control.
- Use Claude Recall when you want every Claude Code session you have ever run to become searchable institutional memory, automatically.
- Use both if you take Claude Code seriously as a collaborator. They cost different things, do different jobs, and never fight over the same file.
Migration and coexistence
There is nothing to migrate. Obsidian reads your vault folder; Claude Recall reads ~/.claude/projects/. They do not touch each other's files. If you already use Obsidian and want to add Claude Recall, install it alongside: npm install -g @clauderecallhq/cli. Your Obsidian vault, plugins, and workflow stay exactly as they are.
FAQ
Can Obsidian replace Claude Recall?
Only if you are willing to manually export every Claude Code session, paste it into Obsidian, and maintain that discipline session after session. People try; few keep it up past month two. Claude Recall automates the capture so you can spend your attention on the actual work.
Does Claude Recall read or modify my Obsidian vault?
No. Claude Recall only reads ~/.claude/projects/ JSONL session files. It never touches your Obsidian vault, never reads your notes, never writes Markdown into your folders.
Can I export Claude Recall sessions into my Obsidian vault?
Yes — Claude Recall can export sessions as plain-text Markdown which you can drop into Obsidian if you want a single graph view across both surfaces. This is opt-in; the default is to keep them in their respective tools.
What does Claude Recall cost?
Free tier for basic usage. Pro is a one-time purchase: $29.69 through May 2026 (Founder pricing), $49.69 lifetime starting June 1, 2026. Never a subscription. See pricing for details.
Keep your Obsidian vault. Add the memory layer for the agent you are steering.
Install Claude Recall→·PricingLast updated April 2026