Paivot Graph
Wire an Obsidian vault into Claude Code so agents, skills, and hooks read live notes and evolve knowledge every session.
Overview
paivot-graph is a plugin marketplace for the Build phase that connects an Obsidian vault to Claude Code so agents, skills, and hooks use vault notes as live runtime context.
What is this marketplace?
- Single plugin: paivot-graph v1.53.14—Obsidian vault as runtime for Claude Code
- Agents, skills, and hooks pull from vault content and update with session activity
- Knowledge graph semantics from Obsidian links map to agent context boundaries
- Session-to-session evolution without duplicating long prompts in chat
- 1 plugin in marketplace: paivot-graph at version 1.53.14
Community signal: 9 GitHub stars.
What problem does it solve?
Your best requirements and decisions live in Obsidian while Claude Code only sees whatever you paste into the current chat.
Who is it for?
Note-first indie builders who already run Obsidian and want Claude Code to respect that graph as project memory.
Skip if: Teams standardized on Notion or Google Docs only, or projects with no local vault discipline.
What do I get? / Deliverables
Agents read and evolve vault-backed knowledge each session, so documentation and implementation context stay aligned without manual copy-paste.
- Claude Code runtime wired to Obsidian vault content
- Session-updated notes that reflect agent work and decisions
- Reusable vault-backed context for skills and hooks
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Build is the primary shelf because the vault becomes executable project memory that agents load while you implement—not a one-time landing or launch task. Docs matches Obsidian-as-runtime: specs, ADRs, runbooks, and graph-linked context that agents reuse instead of re-prompting.
How it compares
Obsidian vault integration marketplace, not a standalone LLM skill or MCP database server.
Common Questions / FAQ
Who is Paivot Graph for?
Developers who keep specs and research in Obsidian and want Claude Code agents and hooks to treat that vault as authoritative context.
When should I use Paivot Graph?
Use it when you are building features and tired of re-uploading the same markdown context every session.
How do I add Paivot Graph to my agent?
Install the Paivot Graph marketplace plugin in Claude Code, point configuration at your Obsidian vault path, then align skills and hooks to the folders and links you want agents to read and update.