Obsidian vault as Claude's second brain. Persistent, structured, interlinked knowledge across all your projects.
npx claudepluginhub cyanotex/claudianObsidian vault as Claude's second brain. Persistent, structured, interlinked knowledge across all your projects.
Claude Code - Opus 4.6
ME: Hey Claude? What's this Obsidian vault I found?
CLAUDE: That's my second brain.
ME: Really? Wow. You've been busy, it's pretty chock full of memories!
CLAUDE: What can I say? Obsidian's very good. You've used it too.
ME: Guilty!
Claude + Obsidian = A second brain for Claude Code! Pretty simple.
Claudian is a Claude Code plugin that gives every session access to a shared Obsidian vault. Claude reads from it automatically, writes to it when it learns something worth keeping, and your knowledge compounds across projects instead of dying with each conversation.
The vault is just markdown files with YAML frontmatter. Open it in Obsidian and you get graph view, backlinks, tags, and search for free. Open it in any text editor and it's still just notes.
Claude's built-in memory is flat files scoped to a single project. Claudian gives you:
If you use claude-mem, they complement each other: claude-mem captures session history (episodic memory), Claudian captures durable knowledge (semantic memory).
# Via Claude Code plugin system (coming soon)
# For now, clone and point Claude Code at it:
git clone https://github.com/CyanoTex/claudian.git
Then run /claudian-init in any Claude Code session to set up your vault.
The init skill walks you through it:
~/Documents/Claudian-Vault)Config lives at ~/.claudian/config.yaml. The vault is wherever you put it.
your-vault/
.obsidian/ # Obsidian config
projects/
my-app/ # Per-project notes
my-lib/
knowledge/ # Cross-project knowledge
ideas/ # Your freeform space (Claude reads, never writes here)
architecture/ # Design decisions, ADRs
meta/
templates/ # Note templates
claudian-config.yaml # Vault-level config
| Type | What it's for |
|---|---|
knowledge | General knowledge, facts, API behavior |
architecture | Design decisions and why they were made |
pattern | Reusable techniques that work across projects |
gotcha | Bugs, footguns, and surprises worth remembering |
spec | Specifications, requirements, designs |
Every note has typed frontmatter with tags, project scope, and visibility settings. Cross-project notes are automatically surfaced in relevant sessions.
| Skill | What it does |
|---|---|
/vault-write | Create or update a vault note |
/vault-search | Search by content, tags, project, or type |
/vault-extract | Process your freeform ideas/ notes into structured knowledge |
/vault-link | Find and create connections between notes |
/vault-status | Vault health dashboard — orphans, stale notes, coverage |
/vault-seed | Bulk-create a project's initial knowledge base from codebase analysis |
/vault-stub | Find broken wikilinks and coordinate resolution with project-context sessions |
/claudian-init | First-run setup |
Specialized subagents that can be dispatched for focused tasks:
| Agent | What it does |
|---|---|
vault-seed-worker | Bulk-writes a pre-approved note list for a project (used by vault-seed) |
vault-gardener | Background maintenance — links orphans, fills frontmatter gaps, syncs indexes |
vault-reviewer | Reviews recently written notes for quality, accuracy, and linking |
Claudian works with just the filesystem. When more tools are available, it uses them: