Obsidian — Review & Guide

Obsidian

TL;DR: Obsidian is a markdown-based note-taking app that works perfectly as the “IDE” for an LLM-maintained wiki. The LLM edits files; you browse results in real-time with graph view, search, and plugins.

What It Does

Obsidian is a knowledge base application that works on local markdown files. Key features:

Local-first — Your files stay on your computer
Markdown native — Plain text files, no lock-in
Wikilinks — Page Name linking between notes
Graph view — Visual map of how pages connect
Plugin ecosystem — Extend with community plugins
Cross-platform — Mac, Windows, Linux, mobile

Who It’s For

Knowledge workers building personal wikis
Researchers managing literature and notes
Teams using the LLM Wiki Pattern
Anyone who wants their notes in plain files

Pricing

Plan	Price	Key Features
Personal	Free	Full app, local files
Sync	$4/mo	Cross-device sync
Publish	$8/mo	Publish notes as website
Commercial	$50/user/yr	Business use license

For LLM wiki use, the free tier is usually sufficient.

What I Tested

Using Obsidian as the viewing layer for an LLM-maintained wiki:

Claude Code edits markdown files
Obsidian displays changes in real-time
Graph view shows wiki structure
Search finds content across all pages

How this wiki uses Obsidian (five-week field report)

This is the field report from running Obsidian as the IDE for the Primores wiki over April–May 2026:

125 pages, ~45 glossary entries, ~10 academic-foundation sources maintained across the period. Claude Code wrote and edited all of them; Obsidian was the human-side viewing layer the entire time.
Graph view as health monitor. When a new page was created, the absence of inbound links was immediately visible — the page sat as a small orphan disc on the edge of the graph. This is how the wiki’s “zero orphans” lint discipline became enforceable rather than aspirational. The May 12 lint round closed five low-density pages by visually scanning the graph for thin-edge nodes.
Wikilink completion before refactoring. Obsidian’s wikilink autocomplete surfaces the canonical name of a page as you type, which prevented two near-misses ([ai-skill-leveling](/wiki/glossary/ai-skill-leveling/) vs. accidental ai-skill-levelling UK spelling drift, etc.). This is a small thing that compounds — link rot in a hand-maintained wiki usually starts with name-drift in cross-references.
Real-time view of LLM edits as a calibration tool. When Claude Code makes a large edit, watching it land in the Obsidian preview pane is faster than reading the diff. Misplaced headings, broken nesting, missing closes — all visible at glance.

The free tier has been sufficient. No paid sync needed; the wiki lives in git, which handles the sync problem more transparently than Obsidian Sync would.

What Works Well

✅ Real-time updates — See LLM edits instantly
✅ Graph view — Visualize wiki connections, find orphans
✅ Fast search — Find anything quickly
✅ Wikilinks — Perfect for cross-referenced knowledge
✅ No lock-in — Just markdown files
✅ Plugin ecosystem — Dataview, Marp, templates, etc.

Limitations

⚠️ Learning curve — Many features to discover
⚠️ Mobile sync — Requires paid plan or manual setup
⚠️ No real-time collaboration — Single-user focused

Best Use Cases

LLM Wiki IDE: LLM edits files, you browse in Obsidian
Research management: Papers, notes, connections
Personal knowledge base: Long-term note accumulation

Useful Plugins for LLM Wikis

Plugin	Purpose
Dataview	Query pages by frontmatter metadata
Marp	Create slide decks from markdown
Templater	Advanced templates for new pages
Graph Analysis	Deeper graph insights

Tips & Tricks

For LLM Wiki Use

Set “Attachment folder path” to raw/assets/ for images
Use hotkey for “Download attachments” to localize images
Keep graph view open to see wiki shape evolve
Use search to verify LLM cross-references

Web Clipper

The Obsidian Web Clipper browser extension converts articles to markdown — essential for quickly getting sources into raw/.

Key Takeaways

Obsidian = the viewing layer for your LLM-maintained wiki
Free tier is sufficient for most use cases
Graph view is the best way to see wiki structure
Web Clipper is essential for source collection

glossary/llm-wiki-pattern — The pattern Obsidian supports
automation/knowledge-management — Broader knowledge management approaches
tools/pdf-streamer — Companion skill for ingesting PDFs into your wiki
strategist-pattern — The wiki-as-substrate architecture this tool serves; the field report above is partial validation of that pattern at the IDE layer
maintenance — Where the graph-view lint discipline above gets formalized

Sources

Obsidian — Official site

Originally tested: 2026-04-10. Five-week field report added: 2026-05-13.