Most AI agents forget everything the moment a session ends, forcing teams to rebuild context from zero on every run. LLM Wikis offer a different approach to agent memory – one that persists, grows, and reorganizes itself over time instead of starting over each time. In this session, Izma Aziz breaks down how LLM Wikis work and why they matter for agents that need to actually remember.
Agent memory has quietly become one of the hardest unsolved problems in applied generative AI. Vector stores and RAG pipelines can retrieve relevant chunks, but they don’t reconcile what they know, resolve contradictions, or restructure themselves as new information arrives. LLM Wikis take a different approach: rather than just storing information, the agent reads, reconciles, and rewrites its own knowledge, much like a human maintaining a living wiki.
This session is built around a live, hands-on build rather than slides alone – you’ll watch an LLM Wiki come together step by step using LangGraph and Deep Agents, with the reasoning behind each design decision explained as it happens. It’s led by Izma Aziz, Senior Software Engineer in Generative AI and LLMs at Data Science Dojo, and grounded in the same architecture and lifecycle her team uses when building agent memory for production systems, not just demos.
This session opens with a clear definition of what LLM Wikis are and why AI agents need memory that actually persists and grows over time, rather than resetting with every new session. From there, Izma draws a sharp distinction between an LLM Wiki and more familiar approaches like RAG, file search, and standard chat history — explaining where each falls short for long-running, evolving agent knowledge.
You’ll also get a walkthrough of the architecture and lifecycle behind an LLM Wiki, from ingesting raw sources through organizing, querying, and updating that knowledge as new information comes in. Rather than treating this as theory, the session includes a live, hands-on build using LangGraph and Deep Agents, showing an LLM Wiki assembled in real time so you can see the moving parts rather than just hear about them.
The session closes by grounding all of this in production reality: the design choices that shape how an LLM Wiki behaves, the limitations you should expect, and what it actually takes to build agent memory you can trust in a live system rather than just a demo.
As agents take on longer-running, more autonomous tasks, the cost of forgetting compounds. An agent that re-derives context on every call burns tokens, adds latency, and risks acting on stale or incomplete information. LLM Wikis address this directly by giving agents a persistent, self-organizing knowledge base — one that can separate what’s true now from what used to be true, and update accordingly instead of accumulating conflicting fragments.
This matters most for teams running agents in production, where memory failures show up as inconsistent answers, repeated mistakes, or ballooning inference costs. For teams thinking through these tradeoffs in more depth, the Data Science Dojo blog covers related patterns in agent architecture, and LangChain’s own work on memory and state management offers a useful complementary perspective on where the field is heading.
This webinar is built for engineers and technical leads who are already building or maintaining LLM-powered agents and want a concrete alternative to RAG for long-term memory — think AI/ML engineers, backend developers working on agent infrastructure, and technical leads evaluating memory architectures for production systems. Some familiarity with LLM agents, RAG, or frameworks like LangChain or LangGraph will help you get the most out of the session, though the live build is designed to be followed even if you haven’t used Deep Agents before.

Senior Software Engineer - Generative AI and LLMs