agricidaniel/claude-obsidian

claude-obsidian

Your AI second brain for Obsidian, built for Claude Code. Drop in sources. Get a connected wiki that grows every time you use it.

Install · See the vault · Skills · Agents · Safety · Modes · FAQ

claude-obsidian turns the things you read into a knowledge base that keeps getting more useful. Drop a paper, an article, a transcript or your own notes into the vault, and Claude reads them, writes linked notes with sources, and files everything into one connected knowledge graph you can explore in Obsidian.

• Capture. Put sources in inbox/. The originals are kept, untouched, so every summary can point back to where it came from.
• Connect. Claude writes linked pages, indexes and maps of content, so new ideas join the graph instead of piling up.
• Ask. Get answers from what your vault already knows, with citations, without changing a single file.
• Save. Keep the answers worth keeping as notes, one at a time, when you ask.
• Check. A health check finds dead links, orphan pages and gaps before they spread.

Everything stays as plain Markdown files on your computer. No cloud database, no lock-in, no telemetry. Apart from the AI tool you chat with, nothing leaves your machine unless you say so.

See the vault

The result is a normal Obsidian vault that stays useful with or without an AI: browse it in Graph view, or lay it out as a map in Obsidian Canvas.

Linked notes in Graph view · A knowledge map in Obsidian Canvas

Install

You need Claude Code, Python 3.11 or newer and, for the visual side, Obsidian. Install the plugin with two commands:

claude plugin marketplace add AgriciDaniel/claude-obsidian
claude plugin install claude-obsidian@agricidaniel-claude-obsidian

Then open the folder you want as your vault and start Claude Code there:

claude                                   # start Claude Code in your vault folder

/claude-obsidian:wiki                    # set up the vault (shows you a preview first)
/claude-obsidian:wiki-ingest             # turn what is in inbox/ into linked notes
/claude-obsidian:wiki-query              # ask a question, answered from your notes
/claude-obsidian:save                    # keep a good answer as a note
/claude-obsidian:wiki-lint               # health check: dead links, orphans, gaps

Open the same folder in Obsidian with Open folder as vault to browse your notes as they grow.

Already have an Obsidian vault? /claude-obsidian:wiki can adopt it without moving your notes. The installation guide walks through it.

15 skills, one system

Talk to it in plain words, or call any skill by name with /claude-obsidian:. Open a group to see what is inside.

Meet the crew

Behind the skills, three agents do the heavy reading and checking. All three are read-only: they hand back drafts and reports, and only one place, the transaction core, ever writes to your vault.

Built for:

• Researchers and students who read a lot and want every note to point back to its source.
• Writers and creators who want ideas from videos, articles and books to connect instead of getting lost in folders.
• Builders and teams who keep project knowledge in Markdown and want an AI that can search it, cite it and keep it tidy.

Nothing gets lost

Your notes matter, so every change to the vault works like a careful save:

1. Read first. Claude reads every note it will touch and records a fingerprint (a SHA-256 hash) of each one.
2. One plan, one apply. Helpers can work in parallel, but they only hand back drafts. Claude merges them into one plan, checks it, and applies it as a single transaction.
3. Undo if anything breaks. A journal keeps backups during the write. If the power cuts out halfway, transaction recover rolls the unfinished change back from the journal.
4. Your edits win. If you change a note in Obsidian while Claude is planning, the fingerprint no longer matches and the write stops with a conflict instead of overwriting you.

Web research, Git checkpoints and anything that sends data off your machine are separate steps that ask you first.

Shape the vault to the way you think

wiki-mode sets how new notes are filed, the way you already like to work. Switching modes changes where new notes go and never moves your old ones.

More in the methodology modes guide.

How it works

1. Capture. Sources go into inbox/. claude-obsidian keeps an untouched copy of each one, named by its content, before anything is summarized.
2. Ground. Each important claim in a note is linked to the source that supports it. Weak or conflicting evidence stays visible instead of being smoothed over.
3. Compound. Ask, research, search and lint use what the vault already knows, so every session starts from your notes instead of from zero.

The idea follows Andrej Karpathy’s LLM Wiki pattern: let the AI maintain a wiki you can read, instead of a black box you cannot.

FAQ

License and contributing

MIT License, see LICENSE. The design follows Andrej Karpathy’s LLM Wiki pattern and uses kepano/obsidian-skills as the reference for Obsidian Markdown, Bases and Canvas syntax. See ATTRIBUTION.md and CITATION.cff.

Contributions are welcome: read CONTRIBUTING.md first and run make test before you open a pull request. Report security problems as described in SECURITY.md, and read PRIVACY.md for what stays on your machine. Release notes live in the changelog, and the code of conduct applies everywhere. AI coding agents working on this repo start at AGENTS.md.

Thank you to everyone who has helped. Pull requests: @Ychris12138, @Marcos64s, @hphsu, @vinsocci, @miraclemanza, @maartengoet, @Lion-1209, @HectorBernstorff, @Packetslave, @CooperSheroy, @yotamleo, @ketpatil77, @tilusnet, @GPezzuti, @STiFLeR7. Issue reports: @RoelKluin, @threnard, @szrenwei, @ppuri2, @cosmos75, @simonc.

Star history

If claude-obsidian helps you, a star helps other people find it.

Author

Built by Agrici Daniel, AI Workflow Architect, with help from the AI Marketing Hub Pro community.