A Note App That Doesn't Own Your Notes
Most note-taking apps share one uncomfortable trait: your notes live on their servers, in their format, accessible only through their interface. Cancel your subscription, change your plan, or watch the company get acquired — and suddenly access to years of thinking is at risk.
Obsidian works differently. Every note you write is saved as a plain .md (Markdown) file on your own machine, in a folder you choose, in a format any text editor can open. No proprietary database. No lock-in. No monthly fee required to read your own thoughts.
But that is not even the interesting part. The interesting part is what Obsidian does with those files once they exist.
How Obsidian Works
Obsidian is built around three core ideas that separate it from traditional note apps.
A vault is just a folder on your computer. Obsidian reads every .md file inside it and turns them into a linked knowledge base. You can have multiple vaults — one for work, one for personal projects, one per client if you want.
Type [[Note Name]] inside any note and Obsidian creates a live link to that note. Click it to jump there instantly. This is how you build a web of connected ideas instead of isolated documents buried in folders.
Every link you create is plotted as a node on a live visual graph. Notes that are heavily linked appear larger. Clusters of related notes form naturally. The graph shows you the shape of your own thinking — connections you never consciously planned.
Add tags like #client or #research to filter notes across your vault. Properties (YAML frontmatter at the top of a file) let you attach structured data — dates, statuses, priorities — to any note.
Search works across every note in your vault instantly — including content inside files, not just titles. With hundreds or thousands of notes, you can find any idea in seconds without remembering which folder it was in.
Obsidian has a community plugin library with hundreds of extensions: Kanban boards, daily journal templates, task trackers, Dataview (query your notes like a database), calendar integrations, and more. Core features are intentionally minimal — plugins handle the rest.
The Graph View: Seeing Your Knowledge
The graph view is the feature that makes Obsidian memorable. It renders every note as a node and every [[link]] as an edge. The result is a visual map of how your thinking is connected.
Each node is a note. Each line is a [[link]]. Hub notes with many connections appear larger automatically.
Over time, the graph reveals something surprising: the connections you did not consciously plan. A note about a client meeting links to a product idea. A journal entry links to a strategic decision. You start to see clusters — groups of ideas that belong together — that you never would have noticed scanning folder names.
Obsidian vs. Older Formats
Most knowledge workers still rely on a mix of Word documents, PDFs, and cloud apps like Notion. Here is how Obsidian compares on the things that actually matter over time.
| What matters | Word / Docs | Notion | Obsidian | |
|---|---|---|---|---|
| File format | Proprietary .docx | Read-only binary | Locked in database | Plain .md text |
| Data ownership | Cloud (Microsoft) | Local, uneditable | Notion servers | Your machine, your folder |
| Works offline | Partial | Yes | Limited | Fully offline |
| Links between notes | Manual hyperlinks only | No | Basic relations | Native [[wiki links]] |
| Visual knowledge graph | No | No | No | Built-in graph view |
| AI-readable | With conversion | With conversion | With API | Native plain text |
| Survives 10 years | Format changes | Yes, but static | Company-dependent | Plain text always works |
| Monthly cost | Subscription required | Free (read-only) | Free tier limited | Free forever (core) |
The longevity argument: A plain .md file written today will be readable on any device in 20 years without any special software. A Notion page or .docx file from 2005 may require active migration just to stay accessible. When you are building a personal knowledge base meant to compound over a career, format durability is not a minor detail — it is the whole foundation.
Obsidian and Claude Code: A Powerful Pair
Claude Code reads plain text files natively. Your Obsidian vault — which is just a folder of .md files — is directly readable by Claude Code without any conversion, export, or plugin.
This opens up a category of AI-assisted workflows that simply do not exist with other note apps.
Point Claude Code at your vault Open a terminal inside your Obsidian vault folder and start Claude Code. It can read every note you have written. Ask it to summarize a specific topic, find contradictions across notes, or generate a new note from existing ones — all without copying and pasting anything.
Turn meeting notes into action items automatically Paste raw meeting notes into a file or write them live. Then ask Claude Code to extract decisions, open questions, and tasks — and write them into a separate [[Action Items]] note. The output is a proper Obsidian note, with links, ready to open.
Query your knowledge base in natural language Ask Claude Code: "What did I write about client onboarding?" or "Summarize everything linked from the Strategy hub note." Since your vault is just files, Claude Code can search and synthesize across hundreds of notes faster than any manual review.
Generate structured notes from a prompt Ask Claude Code to create a new note following your template — with YAML frontmatter, tags, sections, and [[links]] to existing notes in your vault. It writes the file directly, so you open Obsidian and the note is already there, fully formatted.
Use a CLAUDE.md as your vault instruction file Drop a CLAUDE.md file at the root of your vault. Write your note conventions in it: how you tag things, what your hub notes are, what templates you use. Claude Code reads this automatically at the start of every session — so it always works in your style without you explaining it each time.
Two Ways to Use It
Obsidian adapts to very different types of users. The same core features — vault, links, graph — serve a developer managing technical documentation just as well as someone building a personal journal system.
- Architecture Decision Records (ADRs) — log why decisions were made, not just what was built
- Project wikis stored inside the repo as .md files — versioned with git, readable in Obsidian
- Bug investigation notes linked to ticket numbers and affected components
- API documentation drafts that Claude Code can read and refine directly
- Runbooks and on-call playbooks as linked notes — searchable under pressure
- Snippet libraries: code patterns, regex, SQL queries — tagged and searchable
- Daily journal with a template — date, wins, blockers, intentions — linked to weekly reviews
- Book and podcast notes with key ideas tagged by theme, not just by title
- Goal tracking: annual objectives linked to monthly milestones linked to weekly tasks
- Meeting notes from clients or partners, with action items in a separate linked note
- Second brain for ideas — capture anything, let the graph show you what belongs together
- Health, fitness, or habit logs in plain text — private, offline, permanent
Your Notes Should Outlive Every App You Use
Every app you adopt is a bet. A bet that the company stays solvent, that the pricing stays reasonable, that the format stays accessible, that the data export works when you need it. Most note apps ask you to make that bet without mentioning it.
Obsidian does not ask you to bet on anything. Your notes are files. Files do not have licensing agreements or shutdown dates. A folder of .md files you build today will be as readable in 2040 as it is now — whether Obsidian exists or not, whether you have internet access or not, whether the company behind it changes strategy or not.
That is a rare thing to be able to say about a piece of software. It is also, when you think about it, exactly what a personal knowledge base should be: completely and permanently yours.
Start with one vault. Write one note. Link it to one other note. The graph does the rest.