OpenClaw + Obsidian + Claude Code: The AI-Native Dev Setup
The most powerful local development setup I've come across pairs three tools: Claude Code for coding, Obsidian as a knowledge base, and OpenClaw as the bridge that lets your AI coding session pull from your actual research and notes.
The idea comes from Andrej, who built OpenClaw as an open-source approach to giving Claude Code access to a local knowledge graph. The premise is simple but the implications are significant: your AI coding agent shouldn't just know your codebase, it should know everything you know about the domain you're building in.
The stack:
Obsidian is a local-first markdown knowledge base. Every note you take, every research thread, every architecture decision, it lives on your machine as plain text files. No vendor lock-in. You own the data. The vault grows over time and becomes increasingly valuable.
Claude Code runs in your terminal and can read files. Out of the box, it can read your project. With the right setup, it can read your Obsidian vault too.
OpenClaw wires them together, it creates a structured index of your Obsidian vault that Claude Code can query through MCP (Model Context Protocol). You write notes in Obsidian about your domain (ERP architecture, financial systems patterns, API designs), and when you're in a Claude Code session, those notes become part of the context it reasons from.
How Andrej uses it:
- Obsidian vault structured by domain, not by project
- Notes written as "what I know about X" not "notes from meeting on X"
- OpenClaw indexes the vault nightly
- Claude Code sessions start with the relevant domain loaded
My setup:
I use this for ERP and financial systems work. My Obsidian vault has notes on D365 integration patterns, Workday API quirks, SAP data models, and financial consolidation logic. When I'm building something in Aether Ops that touches any of those domains, Claude Code has my accumulated knowledge as context, not just the open files.
The result: it stops asking me to explain things I've already documented. That alone saves hours.
The setup takes about an hour to configure properly. The compounding value starts immediately.