Obsidian
A markdown-based knowledge management tool that stores notes as plain .md files in a local folder, with a visual graph view of the links between them. The reference viewer in Andrej Karpathy's original LLM wiki pattern — used for browsing the LLM-maintained markdown files and exploring page relationships visually.
Key facts
- Type: Markdown note editor + graph view
- Storage: Plain markdown files in a local folder (no database)
- Distinguishing feature: Visual graph view of inter-page links — the inspiration for this wiki's own graph view at
/wiki/wiki-graph/ - Role in Karpathy's pattern: The "IDE" for browsing the LLM wiki. The LLM edits files; the human browses the graph [src-002]
- Memory-system role: Roberts frames Obsidian as the long-term memory option when the user wants readable, editable markdown files, backlinks, visual graphs, and no vector infrastructure [src-059].
What it does
Obsidian treats a folder of markdown files as a "vault" and renders them as an interconnected notebook. Any [[wikilink]] inside a file creates a bidirectional edge between two pages, which is then visible in the graph view — a force-directed visualisation of the whole vault.
In LLM Knowledge Bases (Karpathy pattern), Obsidian plays the role of the browsing layer while Claude Code (or another LLM) acts as the author. The LLM edits the files; the human uses Obsidian to explore the result. This division of labour is the core of Karpathy's LLM wiki pattern: the LLM is the programmer, Obsidian is the IDE, the wiki is the codebase [src-002].
In practice, Obsidian is optional. The wiki is just markdown in a folder — any editor (VS Code, Cursor, Claude Code's terminal UI) works just as well for reading the files. Obsidian adds value specifically because of its graph view, which makes relationships between notes browsable in a way a directory listing cannot [src-002].
In Roberts's three-layer memory system, Obsidian is contrasted with Pinecone. Obsidian is best when the user wants to open, read, edit, and graph memory by hand; Pinecone is better when the goal is semantic search across many records, transcripts, or long documents [src-059].
Roberts's Hermes Agent OS demo uses Obsidian as a shared readable vault for Hermes Agent. The point is not only note-taking: the vault becomes part of the cross-surface memory bridge, so a mobile assistant can answer from the same durable context that the desktop agent environment can inspect [src-079].
Related
- See also: Claude Code, Hermes Agent, LLM Knowledge Bases (Karpathy pattern), AI Memory Operating System, Cross-Harness Memory Bridge, Conversation Wrap-Up Memory, Expert Knowledge Index, Pinecone
Source references
- [src-002] Robin Cartier — "Karpathy's LLM Knowledge Base: A Practitioner's Verdict" (2026-04-08)
- [src-013] Nate Herk — "Build & Sell Claude Code Operating Systems (2+ Hour Course)" (2026-05-01)
– Demo: 36 YouTube transcript nodes visualised in Obsidian with backlinks; Obsidian Web Clipper Chrome extension used to ingest the AI2027 article directly into the raw/ folder, triggering Claude Code to create 23 wiki pages.