Why LLM Wiki? π§ Future Of Knowledge For Agentic AI & Humans
Callum, a former IP lawyer, explains the concept of knowledge graphs and introduces the 'LLM Wiki' β a separate, AI-maintained structured knowledge base that allows multiple AI tools to share the same persistent, interlinked information. He contrasts standard RAG retrieval with graph RAG, arguing that a structured wiki layer dramatically improves how AI handles complex, multi-source knowledge.
Summary
The video begins with Callum introducing two distinct knowledge systems he has built: one for his own thinking (a personal knowledge graph) and a separate one β the LLM Wiki β designed specifically for his agentic AI tools. He frames the video around the foundational building blocks of a knowledge graph: nodes (things, ideas, people, events), edges (named relationships between nodes), and triples (subject-relationship-object), which he describes as the atomic unit of any knowledge graph.
To make knowledge graphs tangible, Callum uses Google's knowledge panel and Wikipedia as real-world examples, noting that both are essentially large-scale knowledge graphs. He then walks viewers through building a knowledge graph in Obsidian using personal examples like favorite inventions, demonstrating how linking concepts while writing naturally produces a graph structure without deliberate graph-building effort. He emphasizes that the graph compounds over time, allowing users to rediscover and build on prior notes rather than starting from scratch.
Callum then transitions to discussing how AI currently retrieves information through RAG (Retrieval Augmented Generation), which converts documents into numerical embeddings and fetches the most similar chunks. While effective for simple queries, he argues RAG fails when answers live in the relationships between documents rather than within individual ones. He introduces graph RAG as a more effective alternative for complex, high-volume data, as it allows AI to follow relational paths between sources rather than retrieving thousands of disconnected chunks.
The video's central concept β the LLM Wiki β is introduced as a solution to the problem of AI tools having siloed, incompatible memories. Callum cites Andrej Karpathy's articulation of the idea: rather than indexing raw documents for retrieval at query time, an LLM incrementally builds and maintains a persistent wiki of structured, interlinked markdown files. When new sources are added, the agent reads, extracts, and integrates them into the existing wiki, updating entity pages and flagging contradictions. This knowledge is compiled once and kept current, rather than rederived on every query.
Callum describes his personal implementation: a separate human vault for his own thinking, and a distinct LLM vault that AI agents build and maintain from raw clipped sources. The LLM Wiki has three layers β raw sources (untouched), a compiled wiki (structured, interlinked pages written by the agent), and ongoing maintenance (contradiction checking, orphan page resolution). He closes by positioning the combination of a human vault and an agentic vault as the closest approximation to a true second brain.
Key Insights
- Callum argues that a knowledge graph is not something you explicitly build β it is the natural byproduct of being specific and relational in how you take notes, stating 'I didn't try to build the graph. I just wrote about the relationship between different concepts.'
- Callum contends that standard RAG fails not when answers live within individual documents, but when they live between documents β in the connections and dependencies β at which point what is needed is 'a reference librarian, not a chatbot.'
- Callum cites Andrej Karpathy's framing of the LLM Wiki: rather than indexing raw sources for retrieval at query time, an LLM incrementally builds a persistent, structured wiki β integrating new information, updating entity pages, and noting contradictions β so knowledge is 'compiled once and kept current, not rederived on every query.'
- Callum explains that AI tools each maintain their own siloed memory, which works within a single tool but breaks down entirely when switching between tools β leading him to propose the LLM Wiki as a shared structured knowledge base that all AI tools can draw from simultaneously.
- Callum deliberately keeps his human vault and LLM vault separate so he can clearly distinguish what came from his own thinking versus what was generated or compiled by AI, describing this separation as a personal 'firewall' between human and machine knowledge.
Topics
Transcript
[0:00] Google built one for the entire internet. I built one for my own brain. And then I built a second one, not for my own thinking, but for my agentic AI tools. A separate brain that AI agents build and maintain automatically so that every AI tool I use shares the same structured knowledge graph. The LLM Wiki has become more popular recently, but it's actually grounded in years of research. To understand how and why it all works, I'll go through what a knowledge graph is, how they can form a wiki for humans and LLMs, and why that matters for the future of AI and knowledge. If you're already taking [0:30] notes, you might just be oneβ¦
Full transcript available for MurmurCast members
Sign Up to AccessMore from Wanderloots
The Future Of AI? π€― Hermes Agent Intro & Benefits #ai #agenticai #hermes
Hermes is an AI agent that improves over time by learning from user workflows, unlike most static AI tools. It automatically identifies recurring patterns, creates reusable skills, and applies them to similar future tasks without explicit training.
One Agent, Many Devices? π§ Full Hermes Agentic AI + Tailscale Workflow
This tutorial demonstrates how to access a single Hermes AI agent from multiple devices using Tailscale VPN and a remote dashboard setup, enabling unified session history, centralized file access, and continuous memory across laptop and desktop without fragmentation.
Safer Agentic AI? π§ Full Docker + Hermes Agent Tutorial (Desktop)
This tutorial demonstrates how to safely run AI agents like Hermes inside Docker containers to sandbox code execution and prevent unauthorized access to sensitive files on your computer. By configuring Docker volumes and mounting specific folders, users can give agents access to only the files they choose while keeping code execution isolated from the main system.
Full Hermes Agent Tutorial (Desktop) π§ A Useful Agentic AI Workflow
This tutorial demonstrates how to set up and use Hermes, an open-source AI agent by Nous Research that learns and evolves over time through persistent memory and automated skill generation. The video covers local model setup with Ollama, cloud model integration with OpenAI, messaging gateway configuration via Telegram, and creating a self-improving daily AI briefing automation.
100% Free & Private AI π¦ Build & Run Local AI Agents #ai #agenticai #ollama #localllm
The video introduces local AI models as a privacy-preserving alternative to cloud-based AI services. By running AI assistants locally on your computer, users can maintain complete control over their data while leveraging AI capabilities for personal tasks like analyzing notes and answering work-related questions.