Obsidian doesn’t ship with Claude built in, but plenty of people run it inside their vault anyway. The reason is simple: an Obsidian vault is just a folder of Markdown files on disk, and Claude Code can read and write text files. So the question isn’t whether you can use Claude with Obsidian — it’s which setup is worth the trouble.

This guide covers the three approaches that have actually caught on in the community, how to set up each one, and an out-of-the-box option if you’d rather skip the plugin wrangling entirely.

The short answer

There are three real ways to use Claude with Obsidian:

  1. The terminal plugin — install a terminal inside Obsidian and run claude in it. The route most r/ObsidianMD threads recommend.
  2. A dedicated Claude plugin — community plugins like Claudian or obsidian-claude-code that embed Claude with a proper UI and inline diffs.
  3. No plugin at all — point the Claude Code CLI straight at your vault folder.

All three work because your notes are plain .md files. The difference is how much setup you do and how much control you get over what Claude changes.

Option 1: The terminal plugin (community favorite)

The most popular approach is to embed a terminal inside Obsidian with the Terminal plugin by polyipseity, then run Claude Code in it. Your vault becomes the working directory, so Claude sees all of your notes.

Setup, step by step:

  1. Install the plugin. In Obsidian, go to Settings → Community plugins → Browse, search for “Terminal” (polyipseity), install it, and enable it.
  2. Open a terminal in your vault. Open the command palette (Cmd/Ctrl+P) and run “Open terminal”. It opens at your vault root by default.
  3. Run Claude. Type claude and start prompting. It reads and edits the .md files in your vault directly.

If claude isn’t found, you need the Claude Code CLI installed and on your PATH first. On macOS, GUI apps don’t always inherit your shell’s PATH, so you may need to point the plugin at the full binary path (e.g. ~/.local/bin/claude).

The tradeoff: it’s a raw terminal. Claude edits your files, but the changes don’t render as reviewable diffs inside your notes — you trust the terminal output and check the file afterward.

Option 2: A dedicated Claude plugin

If you want Claude embedded properly — a sidebar panel, file mentions, inline edits — a purpose-built plugin is a step up from a bare terminal. The two most capable right now:

Both install from a GitHub release (or BRAT for auto-updates), require the Claude Code CLI, and authenticate with either an Anthropic API key or a Claude Pro/Max subscription.

The tradeoff: more polish, but also more moving parts. These are desktop-only, and the most common setup snag — spawn claude ENOENT / “Claude CLI not found” — comes from Node version managers (nvm, fnm, volta) hiding the binary from Obsidian’s Electron environment. You’ll be pasting which claude output into a settings field.

Option 3: No plugin at all

The simplest setup is no plugin. Because your vault is a normal folder, you can run Claude Code against it directly:

cd /path/to/your/vault
claude

That’s it. Claude now operates on your notes with its full toolset. Many experienced users land here — there’s nothing to install or update inside Obsidian, and you get the unmodified Claude Code experience.

The tradeoff: you’re working in a separate terminal window, not inside Obsidian. There’s no in-app UI, no diff rendered in your notes — you alt-tab between Claude and Obsidian.

What all three have in common

Every one of these bolts a terminal or a chat into a notes app. None of them were designed around the thing that actually matters when an AI edits your writing: reviewing what changed before it lands.

With a terminal, Claude writes to the file and you hope nothing got dropped. With most plugins, diff review is partial or varies by tool. The setup friction — CLI paths, PATH issues, auth tokens — is all in service of retrofitting an editor that was never built for agents.

The out-of-the-box alternative: FlashType

If your goal is “Claude editing my markdown, with every change reviewable,” there’s a purpose-built option: FlashType — a free, open-source macOS markdown editor with Claude Code and Codex built in.

You point it at a folder of .md files and the agents work directly on them — no terminal plugin, no PATH debugging, no separate window. The key difference: every edit shows up as an inline diff you accept or reject, one change at a time. Nothing lands until you approve it. It also keeps automatic version history (powered by Lix), so you can roll back without Git.

It’s MIT-licensed and free, including for commercial use.

Is it a replacement for Obsidian? Not for everything. Obsidian’s graph view, backlinks, and plugin ecosystem are unmatched for building a large, interconnected knowledge base. FlashType is the better fit when the priority is editing markdown with AI agents and reviewing every change. Both store plain .md files, so nothing stops you from using both.

Which should you choose?

If you want…Use
Claude inside Obsidian, flexible, you don’t mind a terminalTerminal plugin
A polished in-Obsidian panel with diffsClaudian / obsidian-claude-code
The simplest possible setupClaude Code CLI, no plugin
Out-of-the-box AI editing with diff review built inFlashType

FAQ

Do I need a plugin to use Claude in Obsidian? No. Your vault is a normal folder of .md files, so you can run the Claude Code CLI directly against it. Plugins just give you a nicer in-app experience.

Is there an official Claude plugin for Obsidian? No — there’s no official Anthropic plugin. The popular options are community-built: the obsidian-terminal plugin, Claudian, and Roasbeef’s obsidian-claude-code. All are desktop-only and depend on the Claude Code CLI.

What’s the easiest way to get Claude editing my markdown? If you want it working out of the box with diff review built in, FlashType ships with Claude Code and Codex inside the editor and shows every edit as an accept-or-reject diff — no plugins or terminal setup.