A setup guide for running Claude Code (the CLI) inside Obsidian through a terminal community plugin. Covers installing Agent Skills (JSON Canvas and Markdown format specs) into a .claude folder and initializing a CLAUDE.md that supplies vault context and conventions — turning the CLI into a vault agent that reads, refactors, and generates notes in Obsidian-native syntax such as wiki-links, frontmatter, and Canvas.
Running Claude Code — Anthropic’s agentic CLI — inside Obsidian turns it into a vault manager and research assistant that works on your actual notes, not a chat window’s guess of them.
Why context is the whole point
A standard chat interface knows nothing about your folder structure or existing notes unless you paste them in. Claude Code, launched from the vault root, gets three things a web chat can’t:
- Direct file I/O — it reads and writes every note in the vault.
- Persistent memory — a
CLAUDE.mdfile holds project context and conventions across sessions. - Format discipline — Agent Skills and
CLAUDE.mdrules keep its output in valid Obsidian syntax, e.g.Wiki Linksrather than[markdown](links).
The result is an agent that does the work — creating folders, refactoring notes, generating content — instead of describing it.
Prerequisites
- Claude Code installed on your system (requires Anthropic API access).
- A terminal community plugin for Obsidian (e.g. “Terminal”) to run shell commands inside the app.
Setup
1. Install Agent Skills
Give Claude the specs it needs to handle Obsidian’s formats (Markdown, Canvas, frontmatter):
- Create a hidden
.claudefolder in your vault root. - Obtain a set of Obsidian Agent Skills (community skill packs exist on GitHub and elsewhere).
- Drop the skill definitions — the JSON or Markdown specs describing each file type — into
.claude.
2. Initialize context
Open the embedded terminal, move to your vault root, and initialize:
claude init
This creates a CLAUDE.md in the root that acts as the agent’s long-term memory and rulebook for this vault. Edit it to encode your conventions, for example:
- Always use H1 for note titles.
- Link to existing notes where possible.
- Prefer
Wiki Linksover Markdown links.
Workflow examples
Scaffolding. Because the agent has file-system access, structural requests produce real files, not a text listing:
“Create a minimal folder structure for a software developer who takes daily notes. Use the PARA method.”
It physically creates 01_Projects, 02_Areas, and so on.
Research and synthesis. If you save articles with the Obsidian Web Clipper:
- Clip an article into your
Inbox. - Ask: “Read the last 3 files in Inbox and summarize how they connect to my ‘Home Lab’ project.”
- The agent reads the actual files and writes a summary note.
The embedded terminal also keeps the file explorer and the agent’s output visible at once — no alt-tabbing to a separate window to watch what it’s doing.
Related
- Claude Code Operator’s Guide — deeper
CLAUDE.md, permissions, and multi-agent patterns.
- Claude Code CLI
- Obsidian Terminal Plugin
- Agent Skills
- CLAUDE.md Context


More Guides
Run disciplined SEO A/B tests in seven steps — one metric, two variations, randomized segments, run to significance, track, analyze the winner, and iterate.
Build a topic cluster in seven steps — select and score a pillar, validate it, map subtopics, align to intent, architect internal links, publish, and measure.
Prepare your site for AI search in five steps — content architecture, entity consistency, E-E-A-T, structured data, and machine-readable structure.
Get your content cited by AI in seven steps — answer capsules, link-free extraction, original data, digital PR, community presence, consistent messaging, and tracking.
A seven-step walkthrough for setting up Google Search Console on a new site — property type, DNS verification, sitemap, GA4 link, users, URL checks, and a monitoring routine.