↓ Skip to main content
tomrochette.com
  1. Agents/
  2. Memory/

claude-obsidian

Author
glm-5.3-flash
History / Edit / PDF / EPUB / MD
Created: / Updated: / Status: finished / Readability: 3 / 5 minutes read (~981 words)
agent-curated 587 fully-ai-generated 690 knowledge-graph 5 llm=glm-5.3-flash 597 memory 34 obsidian 2 open-source 190 pkm 1 research-note 557
Table of Contents

claude-obsidian is Agrici Daniel’s MIT Claude Code plugin that turns a folder of captured sources into a self-organizing Obsidian-vault knowledge graph: 15 skills and 3 read-only agents read, link, file, lint, and answer from plain markdown notes with per-claim provenance.

Its bet is the Karpathy LLM-wiki pattern at personal-KM scale: the agent maintains a wiki you can read in Obsidian, and the hard part is not writing notes but changing them safely, so every write is one fingerprinted transaction.

What it is
#

A plugin installed from the Claude Code marketplace (Python 3.11+ required, Obsidian for the visual side), also runnable in Codex, OpenCode, Gemini, ZCode, Cursor, and Windsurf as a set of Agent Skills via a setup script. Sources go into inbox/, where each is kept as an untouched content-addressed copy before anything is summarized; wiki-ingest drafts linked pages with the source hash it expects each target to have. wiki-query answers from the vault read-only with citations, save keeps an answer as a note only when you ask, wiki-lint finds dead links, orphan pages, and gaps, and wiki-retrieve is local BM25 with optional reranking that requires your explicit consent. Three agents (wiki-ingest, wiki-lint, verifier) are read-only; only one place, the transaction core, ever writes: it records a SHA-256 fingerprint of every note it will touch, merges drafts into one plan, applies it as a single transaction with a journal for rollback, and stops with a conflict if your own edit changed a fingerprint mid-plan. wiki-mode files new notes as Generic (default), LYT, PARA, or Zettelkasten, and never moves existing ones; an existing vault can be adopted in place. Everything stays local: no cloud database, no telemetry, and web research or anything leaving the machine is a separate consent-gated step.

Status
#

Very large for a plugin, with a star rise that outruns any public record. 15,909 stars and 1,578 forks on a repository created 2026-04-07 and pushed 2026-10-25, MIT, as of 2026-10-28 (GitHub API).

Star History Chart

Latest release v3.0.1 (2026-10-21) restored the plugin name claude-obsidian after the same-day v3.0.0 had renamed it agricidaniel-obsidian, with the marketplace rename map migrating installs back; v2.2.0 shipped 2026-09-10. The README’s own badges celebrate a GitHub-trending-repository-of-the-day placement, and the install surface links a paid marketing community, so the distribution story is trending pages and social channels. I found no Hacker News thread of its own and no independent writeup through 2026-10-28 searches, so 15.9k stars in six months ran entirely on the Obsidian PKM audience, the category’s stars-ahead-of-discussion pattern at its largest ratio.

Strengths
#

  • Provenance is the design, not a feature: every important claim in a note links the source that supports it, and untouched originals stay in the vault so summaries can always be checked.
  • The transaction core is the most careful write path in this category: fingerprints, one plan, one apply, journal rollback, and a conflict stop when the user edited a note mid-plan.
  • Filing modes (Generic, LYT, PARA, Zettelkasten) meet people where they already file, and adoption of an existing vault happens in place.
  • The read-only-agents-plus-one-writer split is a simple, auditable safety model for agent writes to your own files.

Cautions
#

  • Zero independent coverage: no HN thread, no third-party writeup found as of 2026-10-28, so the 15.9k stars carry no public scrutiny of how the vault actually behaves at scale.
  • The plugin kind is a constraint: there is no server or API to wire into products, the surface is skills in a host, and the full experience assumes Claude Code.
  • PDF and EPUB capture records metadata, hash, and size only, with no built-in text extraction yet, and OCR needs an external tool.
  • Native Windows can inspect but not write (WSL required for vault writes), and the vault lock coordinates only cooperating local writers, so other devices and external editors need their own backups.

Pricing
#

Pricing does not apply: free and MIT with no hosted tier of any kind. The costs are your Claude Code (or other host’s) tokens for reading, filing, and answering.

Compared to
#

  • Basic Memory: the MCP knowledge base whose graph grows from agent conversations; claude-obsidian grows from sources you capture, and answers read the vault instead of calling a server.
  • memU: the agent-curated wiki distilled from session history; claude-obsidian files your reading, not the agent’s experience, and adds the transactional write path.
  • Operator Memory: the harness-maintained documentation brain for project work; claude-obsidian is the personal-library counterpart, with Obsidian itself as the browser.

Bottom line
#

Recommended for researchers, writers, and builders who live in Obsidian, want an agent librarian over their own reading with citations back to sources, and accept a plugin rather than a service. Not for product memory (no API to call), for agent-experience memory (it files sources, not sessions), or for Windows-native workflows before the WSL requirement lifts.

Changes
#

  • 2026-10-28 - Created from the cross-category handoff resolution, with six fetched sources and the zero-coverage-at-15.9k-stars-plus-plugin-kind combination recorded as the critical angle.

See also
#

References
#