🔮 Obsidian, the vault that becomes memory
Where the map becomes memory that you can open, browse, and have the agent consult. A vault is just a markdown folder—and that’s exactly why Claude Code can read everything without friction. Each term is defined the first time it appears.
🗄️ What is Obsidian and a "vault"
O Obsidian is a free note-taking app. Its big idea isn’t a magical format: it opens a text file folder that’s already on your disk and presents it as a connected notebook. This folder has a name of its own — the vault.
🔰 New here? What are "vault" and "markdown"
A vault ("vault") is simply a folder on your computer that Obsidian treats as a collection of notes. No hidden database: it’s the folder you already see in the file explorer.
Markdown is plain text with lightweight markup: # Título, - lista, **negrito**. Each note is a file .md that opens in any editor.
Why does this matter so much in our case? Because a vault isn’t a locked, proprietary file. It’s a folder of .md — so Claude Code reads, does grep and edits everything just like you do. The agent’s memory and your notebook become the same place.
✓ Vault = text folder
- ✓Files
.mdthat open in any editor. - ✓Lives on your disk — works offline.
- ✓Can be versioned with git and read by the agent.
✗ Proprietary format
- ✗Binary database that only one app can open.
- ✗Tied to someone else’s cloud.
- ✗The agent can't read without exporting.
🔑 Key concepts
🔗 Markdown and wikilinks [[...]]
If every graph node becomes a file, one thing is missing: how do you link one note to another? The answer is wikilink — you write the name of another note inside double brackets, and Obsidian turns it into a clickable link. It’s the simplest possible way to say “this connects to that.”
🔰 New here? "Wikilink" and "backlink"
A wikilink is writing [[Nome da nota]] inside a Markdown file: a shortcut that points to another vault note.
A backlink is the way back: if note A links to [[B]], Obsidian automatically shows “↩ referenced by A” in B. You only write the outgoing link; the backlink appears on its own.
# Hooks Hooks são ganchos que rodam em eventos do agente. Eles compartilham a [[Context Window]] da sessão e costumam aparecer perto de [[Subagents]]. ## Relações - usa --> [[Context Window]] - vizinho-de --> [[Subagents]]
↑ A typical vault node note: Markdown text + wikilinks [[Context Window]]. Each graph relationship becomes a clickable link—and the note Context Window gets a backlink pointing back to Hooks.
↑ The cyan arrows are the wikilinks outbound that you write; the dashed green arrow is the backlink that Obsidian creates automatically. This two-way link is what makes the vault navigable in both directions.
🔑 Key concepts
🌐 Obsidian's graph (not the same graph)
Obsidian has a screen called graph view (“graph view”): a bubble of dots and lines, nice to look at. It's tempting to think it é Graphify's knowledge graph — but it's not. It only draws the links between the Markdown notes that exist in the vault.
The difference is subtle, but it matters. The actual knowledge graph (entities, relationships with types, communities, god nodes) lives in graph.json that Graphify generated. Obsidian's graph view is a visual representation of this graph after it becomes notes — it loses the relationship types and leaves only “A links to B.”
⚠️ The video's honest caveat
As the author himself points out: "it's not exactly a knowledge graph, it's a bunch of connected markdown files." The graph view helps browse and view clusters — but the source of truth, with all its richness, remains the graph.json.
graph.json (Graphify)
- •Relationships typed (uses, contains, derives-from).
- •Communities and calculated god nodes.
- •Provenance: which file each thing came from.
graph view (Obsidian)
- •Just “A links to B” — an untyped link.
- •Great for see and click through the clusters.
- •It's a diagram of the vault, not the source.
🔑 Key concepts
🤝 Why Markdown works well with Claude Code
Here’s the fit that makes the whole stack work: Markdown is plain text. There’s no binary layer, no proprietary database, no conversion. The same file .md that you enjoy reading in Obsidian is exactly what Claude Code opens, does grep and edits.
And the wikilinks don't get in the agent's way — they help. When Claude Code reads a note and finds [[Context Window]], it has the exact name of the next note to open. The link is human-readable e per machine at the same time. No lock-in, no secret format: the memory stays in a format that survives any tool.
✓ Markdown (plain text)
- ✓The agent reads directly, without exporting.
- ✓grep and editing work line by line.
- ✓You and the machine read the same file.
✗ Binary format
- ✗Requires a specific app to open.
- ✗grep returns junk; the agent gets stuck.
- ✗Lock-in: held hostage by a single tool.
🔑 Key concepts
🧰 Plugins, canvas, and infrastructure
Many people choose this stack not just for Markdown, but for its infrastructure around it: a pleasant interface, search, themes, and hundreds of extensions. Two names come up all the time — canvas e plugins — and it’s worth knowing what each one does.
🔰 New here? "Canvas" and "plugin"
O Canvas is an infinite Obsidian canvas: you drag notes, boxes, and arrows around a visual space, like a bulletin board. Graphify generates a file graph.canvas with the communities already grouped and named.
A plugin is an extension that adds features to Obsidian (advanced search, tables, kanban, etc.)—like a browser add-on, but for your notebook.
vault/ ├── Context Window.md ← nota de nó (com [[wikilinks]]) ├── Hooks.md ├── Subagents.md ├── graph.canvas ← comunidades como grupos no Canvas └── .obsidian/ ← config, temas e plugins do vault
↑ The anatomy of a generated vault: the notes .md, o graph.canvas with the clusters, and the folder .obsidian/ where themes and plugins live. All text, all on your disk.
Canvas = visual map
Graphify communities become named groups on a board you can explore visually.
Plugins = extra features
Search, pivot tables, visualizations—you enable only what you need, without editing the notes.
🔑 Key concepts
🌉 The connection: from graph.json to the vault
Now the two margins meet. On one side, the graph.json — the graph’s source of truth. On the other side, the vault—the memory you open and the agent consults. The export Obsidian is the bridge: it reads the graph.json and writes a file .md per node, with the wikilinks already in place.
One detail that closes the loop: the vault is regenerated with each export. The source of truth is never the markdown — it’s always the graph.json. If the graph changes, you re-export it and the vault updates. That's why Track 1 ends here: you already understand both sides e the bridge between them. Track 2 crosses that bridge in practice.
↑ The entire Track 1 bridge in one image: the graph.json (source) spans the export and becomes a fan of .md — the vault that Claude Code consults. Regenerated the graph? Re-export it, and the vault stays in sync.
🔑 Key concepts
✋ Self-recovery (optional, non-blocking): if the note Hooks.md writes [[Context Window]], what Obsidian creates alone in the note Context Window.md?
📌 Module summary
Next: Track 2 · Hands-on step-by-step
That’s the end of the fundamentals. Now you install Graphify, choose the source, generate the graph, and create the Obsidian vault in practice.