🚀 Real-world and advanced use
With your second brain set up: how to ask questions using the graph, build a Claude OS, decide between code and documents, and keep the vault alive without letting it become a mess.
progress
↑ O Claude OS as a command center: your question goes to the center, which queries graph, notes, projects e questions in parallel—and the answers converge back in one place.
Trail map
Detailed content
💬 Ask Claude Code using the graph
With the vault in the project, make the agent respond using the map instead of scanning everything.
Keep the vault inside (or alongside) the project and tell Claude Code where it is.
It only uses what it can see — if the vault isn't in context, it's as if it doesn't exist.
Vault path · context · project.
Use the god nodes from GRAPH_REPORT.md as a starting point for questions.
Hubs cover more ground—starting with them brings the rest of the map along.
God node · hub · entry point.
Ask it to follow the [[links]] from one concept to its neighbors.
Connected answers, not isolated ones — the agent moves through neighboring nodes instead of stopping at the first one.
Backlink · neighborhood · navigation.
Ready-to-use prompt — "use the vault in <folder> to explain X and its related concepts, citing the notes".
Directs the agent to the graph instead of letting it scan files blindly.
Prompt · cite notes · scope.
graphify --mcp exposes tools query_graph, get_node, shortest_path.
The agent queries the graph programmatically, without relying only on the markdown files.
MCP · query_graph · resource.
Go from the concept to the linked source doc and check that it matches.
Prevents hallucinations and closes the loop: provenance takes you back to the evidence.
Provenance · verification · source doc.
🏛️ Building a Claude OS command center
Turn the vault into a command center: multiple projects, knowledge, and questions in one place.
A main vault that brings projects, content, and imported knowledge together in a coherent system.
The stack shines when it’s part of a whole—not as disconnected graphs.
Command center · main vault · system.
Organize the vault into projects/areas and a folder for graph imports.
Everything in its place, easy to find—and easy for the agent to navigate.
PARA-like · projects · imports.
Each new Graphify goes into an import subfolder and links to what’s already there.
The brain grows in a controlled, curated way instead of becoming a dump.
Subfolder · connection · curation.
Create bridge notes that connect the imported knowledge to your real projects.
Gets the graph out of a vacuum — the video’s thesis: integrated knowledge is more valuable than isolated knowledge.
Bridge note · context · integration.
Use the agent to query, summarize, and update the command center vault.
The center stays alive, not static—it edits alongside you.
Copilot · query · maintain.
For code bases or one-off queries, stopping at Graphify may be better.
Not every case calls for Obsidian — setting up a hub just for one question is overhead.
Trade-off · silo · simplicity.
🧭 Code vs. documents: when to stop at Graphify
Not every graph needs to go into Obsidian. Learn when to stop.
Point Graphify to a code repository (AST extraction via tree-sitter).
Maps functions/modules without an API key—fast and cheap.
Code base · AST · tree-sitter.
Point to docs/PDFs (semantic extraction via LLM).
Captures concepts and relationships in text—not just the literal structure.
Corpus · LLM · semantics.
For exploring a specific code base, graph.html + query are enough.
Moving it to Obsidian would be overhead when you just want a quick answer.
Stop · graph.html · query.
When knowledge needs to live alongside your projects and notes.
It’s the use case for an integrated second brain — not an isolated graph.
Integrate · vault · larger context.
Use graphify update/--watch as the code/docs change.
The graph doesn’t age—it stays true to the source.
Update · watch · sync.
Weigh extraction time, graph noise, and the effort of maintaining the vault.
A conscious decision, not hype—the cost is real.
Cost · noise · maintenance.
🛠️ Maintenance, updates, and troubleshooting
Keep the graph and vault healthy, and know what to do when something goes wrong.
graphify update . reprocesses only what changed; re-export the --obsidian regenerates the vault.
Keep it current without rebuilding everything from scratch.
Update · re-export · incremental.
The Obsidian export is regenerated from scratch—manual edits to the generated notes are lost.
Keeping your notes in separate folders (imports vs. yours) protects your work.
Regeneration · separation · imports.
Run uv tool update-shell and reopen the terminal.
The binary isn't in the PATH—the shell needs to reload.
PATH · shell · uv.
Set ANTHROPIC_API_KEY for headless use; inside the /graphify doesn't need to.
Distinguishing the two paths avoids a key error where no key is needed.
API key · headless · skill.
Clean the source, use --mode deep or re-scope.
Improves entities/relationships—better corpus, better graph.
Noise · --mode deep · scope.
Commit graphify-out/ (or the vault) in git; use the course's own export to save your progress.
Reproducible and safe — you won't lose what you built.
Git · backup · reproducibility.