By cyanotex
Obsidian vault as Claude's second brain. Persistent, structured, interlinked knowledge across all your projects.
Background maintenance agent that audits vault health and fixes common issues — orphan notes, missing links, stale content, frontmatter gaps. Run periodically or after bulk writes.
Reviews recently written vault notes for quality, accuracy, and proper linking before they settle into the knowledge base. Run after vault-write or vault-seed.
Subagent that writes vault notes from approved descriptions. Dispatched by vault-seed Phase 3 with note metadata and codebase context to produce real content.
First-run setup for Claudian. Creates the Obsidian vault structure, writes the global config at ~/.claudian/config.yaml, and registers projects. Use when no Claudian config exists or when the user wants to reconfigure.
Process the user's freeform notes in the vault's ideas/ folder into structured knowledge notes. Use when SessionStart flags unprocessed ideas, or when the user asks you to look at their ideas.
Summarize an archived graphify knowledge-graph report — cross-cluster bridges, hyperedges, knowledge gaps — and surface Claudian actions. Use when asked about the shape of the vault, ambient connections, or synthesis candidates.
Find and create connections between existing vault notes. Use after writing a new note, or when you notice notes that should reference each other but don't.
Bulk-create a project's initial knowledge base in the Claudian vault. Analyzes the project codebase, proposes a set of interconnected notes, and writes them after user approval. Use when a project is first registered or when you need to populate a project's vault presence from scratch.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
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-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:
npx claudepluginhub cyanotex/claudian --plugin claudianBidirectional knowledge flow between Claude Code and Obsidian — 20 MCP tools, skills, and hooks for PKM
Persistent Obsidian-based memory for coding agents. Automatically orients from a knowledge vault at session start, navigates project architecture via graph traversal, and writes discoveries back to the vault.
Create and edit Obsidian vault files including Markdown, Bases, and Canvas. Use when working with .md, .base, or .canvas files in an Obsidian vault.
A self-developing knowledge management system for Claude Code. Bridges AI memory to an Obsidian vault with feature-organized spine notes, auto-capture skills, and color-coded graph visualization.
Give your AI coding agent a permanent second brain. Connect Claude Code to an Obsidian vault to auto-record decisions, instantly recall project context, and orchestrate automated refactoring for your team's knowledge base.
Automatic Claude Code -> Obsidian second brain: zero-config session capture, hybrid search, autonomous recall, daily/lessons/preferences.