#Obsidian Notes (Claude Code plugin)

Claude Code plugin: a skill and a /obsidian-note command that persist documentation, decisions, and summaries as Markdown notes in your Obsidian vault, by shelling out to the obsidian-notes-cli. This repo has no logic of its own beyond that — no parsing, no vault access, no frontmatter building. The CLI does all of it.

Part of a 3-repo integration:

• obsidian-notes-cli — does the actual writing; this plugin is a thin wrapper around it.
• obsidian-claude-notes — Obsidian plugin (sidebar, live refresh) for browsing what gets written.
• claude-code-obsidian-notes (this repo).

#Requirements

• obsidian-notes-cli on PATH (or resolvable another way — see Install)
• A vault path the CLI can resolve: --vault flag, OBSIDIAN_VAULT env var, or a persisted default from vault:config

#What's in this repo

#Install

composer global require jeffersongoncalves/obsidian-notes-cli

Then in Claude Code:

/plugin marketplace add jeffersongoncalves/claude-code-obsidian-notes
/plugin install obsidian-notes

Set OBSIDIAN_VAULT to your vault's path, or persist a default the CLI will fall back to automatically:

export OBSIDIAN_VAULT=/path/to/vault
# or, to persist a default (new vault — scaffolds .claude-notes.json too):
obsidian-notes vault:init /path/to/vault
# or, to point the default at an existing vault:
obsidian-notes vault:config /path/to/vault

#Usage

/obsidian-note "Decision: use SQLite"

saves the current conversation's relevant content under that title. Or just ask in plain language — any of these trigger the skill:

• "salva isso no obsidian"
• "documenta essa decisão no obsidian"
• "anota isso no obsidian"
• "save this to my Obsidian notes"
• "persist this as an Obsidian note"

Nothing is written automatically at the end of a session, and there's no hook wired up for it — only an explicit ask (skill trigger or slash command) ever writes a note. If you want session-end auto-capture, that's a deliberate scope cut, not an oversight — add a Stop hook calling the CLI yourself if you want it.

#How it resolves things

• Vault: the CLI's own precedence — --vault flag, then OBSIDIAN_VAULT env var, then the persisted default from vault:config. The skill only passes --vault when the user gave an explicit path; otherwise it lets the CLI resolve it. (.claude-notes.json lives in the vault root and holds folderPattern/frontmatterDefaults — it's not part of vault-path resolution.)
• Project: the current repo's folder name, or its git remote get-url origin basename when available — this is what groups notes both in the vault's folder structure and in the Obsidian plugin's sidebar.
• Body: written as clean Markdown and piped to the CLI over stdin — no frontmatter added here, the CLI handles source/project/title/tags/created/updated itself.

If none of --vault, OBSIDIAN_VAULT, or a persisted vault:config default resolves, the skill asks for a vault path rather than guessing one.

See skills/obsidian-notes/SKILL.md for the exact logic Claude Code follows.

#License

MIT.