TAU-HOME.COM
LOADING

claude-obsidian: An Open-Source AI Second Brain Connecting Obsidian and Claude Code

Discover claude-obsidian, an open-source tool that reads incoming documents in an inbox folder and organizes them into a connected local Markdown knowledge grap

tau · November 15, 2026

#claude-code #obsidian #second-brain #pkm #open-source

claude-obsidian: An Open-Source AI Second Brain Connecting Obsidian and Claude Code

Collecting digital references is effortless, but organizing them into a coherent personal knowledge base is notoriously difficult. Many people save articles, research papers, and meeting notes into an inbox folder, only for those files to accumulate without ever being revisited. The open-source tool claude-obsidian automates this personal knowledge management (PKM) bottleneck by bridging Anthropic's terminal agent Claude Code with the local note-taking software Obsidian.

Knowledge graph view in Obsidian integrated with Claude Code via claude-obsidian

Image source: https://x.com/dopamine_crypto/status/2121872077619667225

Created by developer AgriciDaniel and licensed under the MIT License, claude-obsidian turns unstructured inputs into an interconnected knowledge web. Whenever a user places documents or text files into an inbox/ directory, Claude reads the material, distills key insights, and generates linked Markdown notes that automatically form an Obsidian knowledge graph. Following the v3.0.1 release on October 21, 2026, which stabilized the plugin namespace, the repository has surpassed 16,000 stars on GitHub.

Karpathy's LLM Wiki Pattern and Three-Agent Architecture

At the structural core of claude-obsidian lies the 'LLM Wiki pattern' originally conceptualized by AI researcher Andrej Karpathy. Rather than treating an artificial intelligence model as a transient chat window where answers vanish after a session, the system treats knowledge accumulation like maintaining an encyclopedia. Each incoming document triggers updates to indexes, concept pages, and cross-references, allowing the overall vault to expand organically over time.

To preserve reliability, the system isolates duties across three read-only agents and a dedicated transaction core:

  • wiki-ingest Agent: Reads unprocessed sources deposited in inbox/ and drafts new interconnected pages. Original files remain untouched, ensuring every distilled summary retains direct traceability back to its original source.
  • wiki-lint Agent: Executes periodic health checks across the vault, identifying broken internal links, isolated orphan pages with no inbound links, missing frontmatter properties, and empty sections.
  • verifier Agent: Tests and evaluates proposed modifications before any writes occur, verifying that new additions do not compromise vault consistency.

Because all three specialized agents operate in read-only mode, files are never modified arbitrarily. Actual disk operations are strictly handled by the verified transaction core.

Data Integrity Through Single Transactions and Journal Rollbacks

A primary concern when pairing autonomous AI models with local file directories is the risk of silent file overwrites or corrupted notes. claude-obsidian mitigates this by enforcing atomic transactions protected by SHA-256 hash checks alongside a journal rollback mechanism.

Every modification batch is pre-computed and validated before being written to disk. If a network interruption occurs, an agent halts, or a link mismatch is detected, the transaction aborts and cleanly reverts back to the preceding state recorded in the journal.

Crucially, the resulting output consists purely of plain Markdown files stored on the user's local drive. There is no external proprietary cloud database, no third-party lock-in, and no mandatory data telemetry. Users retain full ownership of their files and can navigate their vault using Obsidian's native Graph view and Canvas boards, with or without an active AI session.

System Workflow: 15 Skills and Diverse Filing Modes

claude-obsidian exposes a comprehensive modular architecture containing 15 specialized skills, grouped into five core workflow skills, seven extensions, and three reference modules. Users can interact through everyday conversational prompts or invoke skills directly using command prefixes:

  • Core Workflows: Commands include /claude-obsidian:wiki to initialize a new vault or adopt an existing folder, /claude-obsidian:wiki-ingest to transform inbox documents into linked notes, /claude-obsidian:wiki-query to query existing notes with citations, /claude-obsidian:save to preserve key answers as permanent notes, and /claude-obsidian:wiki-lint to run vault integrity audits.
  • Filing Methodologies: The wiki-mode skill allows users to tailor note organization to their preferred knowledge management framework. Beyond the default Generic mode, the system supports Zettelkasten, PARA (Projects, Areas, Resources, Archives), and LYT (Linking Your Thinking) organizational conventions.
  • Search and Canvas Extensions: The tool integrates local BM25 keyword search capabilities (wiki-retrieve) with optional reranking, alongside programmatic Obsidian Canvas generation (canvas) for visual mapping.

Prerequisites and Installation Guide

Running claude-obsidian requires an active Claude Code environment, Python 3.11 or newer, and the Obsidian desktop application for browsing the resulting visual vault.

Installation can be completed in an authorized terminal session with two plugin commands:

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

Once installed, navigate to the local folder intended for your notes and start Claude Code:

claude
/claude-obsidian:wiki

The setup sequence presents an upfront preview before generating vault folders or modifying files upon user confirmation. Existing Obsidian vaults can be adopted in place without restructuring or moving existing notes.

For Windows users, conducting vault write operations inside WSL (Windows Subsystem for Linux) is recommended. While native Windows environments can inspect files and run preview commands, direct vault write operations require POSIX compatibility for file transaction safety.

Sources

Impact-Site-Verification: 9b3ebd10-6c45-44cf-a014-5b8c19b7b285