Loading video...

Video Failed to Load

Go Home

Make any knowledge base or LLM wiki follow the Open Knowledge Format with our new OKF plugin. OKF is an open spec created by Google that makes markdown-based knowledge bases portable and interoperable through a set of shared patterns and rules. With the new plugin, you can easily convert...

openknowledge's profile picture

OpenKnowledge

2,796 subscribers

139,843 views • 1 month ago •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

AI Agents can take your business to the next level, and Bird makes set up easier than ever. Dive into our Knowledge Base to learn how and explore a range of other valuable resources.
0:14

AI Agents can take your business to the next level, and Bird makes set up easier than ever. Dive into our Knowledge Base to learn how and explore a range of other valuable resources.

Bird

28,711 views • 1 year ago

I just open-sourced my /learn skill. Learn anything with agents and HTML artifacts. I have been learning about all kinds of topics with it. Install the skill and interact with any agent to help you through any topic. Ask it to generate visual and interactive artifacts and help you go deeper or generate knowledge checks (e.g., quizzes). Upskilling myself on any topic is one of the most impactful ways I have been able to use AI agents. If you are a DAIR Academy pro member, you can use it with our AI Builder. Skill: Try now:
0:19

I just open-sourced my /learn skill. Learn anything with agents and HTML artifacts. I have been learning about all kinds of topics with it. Install the skill and interact with any agent to help you through any topic. Ask it to generate visual and interactive artifacts and help you go deeper or generate knowledge checks (e.g., quizzes). Upskilling myself on any topic is one of the most impactful ways I have been able to use AI agents. If you are a DAIR Academy pro member, you can use it with our AI Builder. Skill: Try now:

elvis

35,136 views • 3 months ago

BUILD KARPATHY'S SECOND BRAIN WITH CLAUDE FABLE 5 + OBSIDIAN Andrej Karpathy (openai co-founder) shared an architecture that turns Claude into a persistent second brain instead of a basic chat window how it works: > you point Claude Code at an Obsidian vault folder > you drop articles, PDFs, or video transcripts into raw folders > Claude reads the files, updates topic summaries, and cross-references everything > the knowledge base compounds like interest instead of resetting on every new chat the setup is simple: > install and create a local vault directory > open the directory in Claude Code and paste Karpathy's wiki prompt: > > let the agent generate raw, wiki, and CLAUDE.md schema directories > drop any text file into raw and tell the model to ingest it > ask questions across the whole vault and query compiled summaries this eliminates rag database overhead and keeps your local vault organized how do you manage your local knowledge base?
0:11

BUILD KARPATHY'S SECOND BRAIN WITH CLAUDE FABLE 5 + OBSIDIAN Andrej Karpathy (openai co-founder) shared an architecture that turns Claude into a persistent second brain instead of a basic chat window how it works: > you point Claude Code at an Obsidian vault folder > you drop articles, PDFs, or video transcripts into raw folders > Claude reads the files, updates topic summaries, and cross-references everything > the knowledge base compounds like interest instead of resetting on every new chat the setup is simple: > install and create a local vault directory > open the directory in Claude Code and paste Karpathy's wiki prompt: > > let the agent generate raw, wiki, and CLAUDE.md schema directories > drop any text file into raw and tell the model to ingest it > ask questions across the whole vault and query compiled summaries this eliminates rag database overhead and keeps your local vault organized how do you manage your local knowledge base?

Mr. Buzzoni

89,170 views • 3 months ago

HERMES AGENT HAS A SECOND BRAIN. 1,100+ KNOWLEDGE FILES. AUTO-LINKED. SELF-IMPROVING. GROWING EVERY NIGHT. THIS IS THE OBSIDIAN GRAPH BEHIND IT. every dot = one knowledge file (markdown) every line = one wiki-link between files every color = one category (skills, notes, decisions, sources, entities) HOW IT BUILDS ITSELF: Hermes ships with a bundled LLM Wiki skill. based on Andrej Karpathy's pattern. unlike RAG (rediscovers knowledge from scratch every query), the wiki compiles knowledge once and keeps it current. when you feed the agent a source: → it reads the content → writes a structured markdown page → auto-links to every related existing page → flags contradictions with previous entries → updates all affected pages one source in. multiple connections created. the graph grows denser with every entry. WHAT FEEDS THE WIKI: → articles and URLs you find interesting → meeting transcripts → PDF documents and research papers → conversation history from Hermes sessions → Claude Code and Codex session history → Slack logs, email threads, saved notes → YouTube transcripts → raw text dropped into a _raw/ folder the obsidian-wiki package supports multi-agent ingest from Hermes, Claude Code, Codex, OpenClaw, Pi, Windsurf, and ChatGPT exports. install: pip install obsidian-wiki obsidian-wiki setup --vault ~/wiki AUTOMATE THE GROWTH: set cron jobs to feed the wiki overnight: "every day at 9am, check for new meetings. ingest transcripts into the wiki." "every week, check arXiv for new papers in [niche]. summarize and file into the wiki." "every day, ingest today's Hermes sessions into the wiki under session-history." month 1: 50 entries. scattered. month 3: 300+ entries. cross-referenced. month 6: 1,000+ entries. the agent surfaces patterns you never searched for. WHY OBSIDIAN: the wiki is plain markdown files. no database. no lock-in. open it in Obsidian for graph view: → nodes show knowledge density → links show how ideas connect → clusters reveal your strongest domains → orphan nodes reveal gaps Hermes writes from a VPS. Obsidian reads on your laptop. obsidian-headless syncs without a GUI. agent writes from the server, you browse on your device. FOUR MEMORY LAYERS: Layer 1: memory.md + user.md (~2,200 + 1,375 chars. short-term.) Layer 2: SQLite with FTS5 (full session transcripts. searchable.) Layer 3: external providers (Mem0, SuperMemory, Honcho. optional.) Layer 4: Obsidian wiki via LLM Wiki skill (unlimited. compounding. the long-term brain.) layers 1-3 handle memory. layer 4 handles knowledge. the graph in this post is layer 4. SETUP: set in Desktop app, Dashboard, or config.yaml: WIKI_PATH=~/wiki OBSIDIAN_VAULT_PATH=~/wiki first run: Hermes asks for your domain. answer with your niche. the skill builds SCHEMA.md with tag taxonomy. after that: "index this into my wiki: [URL or text]" the wiki grows. the graph densifies. the agent gets smarter because the knowledge base got smarter. full 15 levels breakdown in the article 👇
0:11

HERMES AGENT HAS A SECOND BRAIN. 1,100+ KNOWLEDGE FILES. AUTO-LINKED. SELF-IMPROVING. GROWING EVERY NIGHT. THIS IS THE OBSIDIAN GRAPH BEHIND IT. every dot = one knowledge file (markdown) every line = one wiki-link between files every color = one category (skills, notes, decisions, sources, entities) HOW IT BUILDS ITSELF: Hermes ships with a bundled LLM Wiki skill. based on Andrej Karpathy's pattern. unlike RAG (rediscovers knowledge from scratch every query), the wiki compiles knowledge once and keeps it current. when you feed the agent a source: → it reads the content → writes a structured markdown page → auto-links to every related existing page → flags contradictions with previous entries → updates all affected pages one source in. multiple connections created. the graph grows denser with every entry. WHAT FEEDS THE WIKI: → articles and URLs you find interesting → meeting transcripts → PDF documents and research papers → conversation history from Hermes sessions → Claude Code and Codex session history → Slack logs, email threads, saved notes → YouTube transcripts → raw text dropped into a _raw/ folder the obsidian-wiki package supports multi-agent ingest from Hermes, Claude Code, Codex, OpenClaw, Pi, Windsurf, and ChatGPT exports. install: pip install obsidian-wiki obsidian-wiki setup --vault ~/wiki AUTOMATE THE GROWTH: set cron jobs to feed the wiki overnight: "every day at 9am, check for new meetings. ingest transcripts into the wiki." "every week, check arXiv for new papers in [niche]. summarize and file into the wiki." "every day, ingest today's Hermes sessions into the wiki under session-history." month 1: 50 entries. scattered. month 3: 300+ entries. cross-referenced. month 6: 1,000+ entries. the agent surfaces patterns you never searched for. WHY OBSIDIAN: the wiki is plain markdown files. no database. no lock-in. open it in Obsidian for graph view: → nodes show knowledge density → links show how ideas connect → clusters reveal your strongest domains → orphan nodes reveal gaps Hermes writes from a VPS. Obsidian reads on your laptop. obsidian-headless syncs without a GUI. agent writes from the server, you browse on your device. FOUR MEMORY LAYERS: Layer 1: memory.md + user.md (~2,200 + 1,375 chars. short-term.) Layer 2: SQLite with FTS5 (full session transcripts. searchable.) Layer 3: external providers (Mem0, SuperMemory, Honcho. optional.) Layer 4: Obsidian wiki via LLM Wiki skill (unlimited. compounding. the long-term brain.) layers 1-3 handle memory. layer 4 handles knowledge. the graph in this post is layer 4. SETUP: set in Desktop app, Dashboard, or config.yaml: WIKI_PATH=~/wiki OBSIDIAN_VAULT_PATH=~/wiki first run: Hermes asks for your domain. answer with your niche. the skill builds SCHEMA.md with tag taxonomy. after that: "index this into my wiki: [URL or text]" the wiki grows. the graph densifies. the agent gets smarter because the knowledge base got smarter. full 15 levels breakdown in the article 👇

YanXbt

35,900 views • 3 months ago

LLM Knowledge Base → Slides When Andrej Karpathy shared his LLM Knowledge Base setup, many were wondering how to generate more visual forms of the wiki. There are many options, but I think Gamma is one of the best at producing high-quality, rich presentations. To showcase this, I just built a pipeline that turns my AI papers wiki (1K+ papers across 20 AI agent topics) into polished slide presentations using Gamma. The flow: Obsidian vault → Gamma MCP → embedded preview in my dashboard. I give one command to my agent, which pulls the top papers from each topic (via the wiki), feeds them to Gamma, and renders the presentation inline. The Gamma connector for Claude is a great choice for generating beautiful and professional slides. Easy to use. Go to your Claude instance and add the official Gamma connector. That's it! Claude Code will now have access to all the necessary MCP tools for generating slides. I use the Claude Agent SDK for my agent orchestrator, so I use the official Gamma MCP tools and embed the generated slides in an iframe via my artifact preview. See the clip below for an example.
0:19

LLM Knowledge Base → Slides When Andrej Karpathy shared his LLM Knowledge Base setup, many were wondering how to generate more visual forms of the wiki. There are many options, but I think Gamma is one of the best at producing high-quality, rich presentations. To showcase this, I just built a pipeline that turns my AI papers wiki (1K+ papers across 20 AI agent topics) into polished slide presentations using Gamma. The flow: Obsidian vault → Gamma MCP → embedded preview in my dashboard. I give one command to my agent, which pulls the top papers from each topic (via the wiki), feeds them to Gamma, and renders the presentation inline. The Gamma connector for Claude is a great choice for generating beautiful and professional slides. Easy to use. Go to your Claude instance and add the official Gamma connector. That's it! Claude Code will now have access to all the necessary MCP tools for generating slides. I use the Claude Agent SDK for my agent orchestrator, so I use the official Gamma MCP tools and embed the generated slides in an iframe via my artifact preview. See the clip below for an example.

elvis

47,989 views • 6 months ago

Build AI agents on a time-aware knowledge graph! Utopia is an open-source knowledge system that turns documents, databases, and connected sources into a temporal graph your agents can reason over. Most RAG systems are optimized for one question: what is relevant right now? That works until the underlying knowledge changes. A customer contract gets updated. A project owner changes. A policy is revised. A previous fact may no longer be true, but simply overwriting it means the system loses the history behind that change. Utopia handles this with a bitemporal knowledge graph. Each fact can track both when it was true in the real world and when the system learned about it. When something changes, the old fact is preserved instead of silently disappearing. That means an agent can reason about questions like: • What is true now? • What was true three months ago? • When did this information change? • What evidence was the conclusion based on? The graph is also ontology-aware, so documents are represented as entities, facts, and relationships instead of only chunks and embeddings. That gives the system more structure for reasoning across relationships, resolving entities, detecting conflicting facts, and deriving new information through explicit rules. Key capabilities: • Bitemporal knowledge graph for tracking how facts change over time • Provenance on facts so agents can trace where information came from • Conflict detection instead of silently overwriting contradictory information • Ontology-based reasoning across entities, relationships, and derived facts • Hybrid retrieval across full-text search, vector search, and graph traversal • MCP and agentic RAG support for exposing the knowledge layer directly to agents The interesting part is that this turns the knowledge base into more than a retrieval system. Instead of only finding relevant information, an agent can reason over what changed, what is still valid, how facts are connected, and where each conclusion came from. 100% open source. I've shared the GitHub repo in the comments!
0:16

Build AI agents on a time-aware knowledge graph! Utopia is an open-source knowledge system that turns documents, databases, and connected sources into a temporal graph your agents can reason over. Most RAG systems are optimized for one question: what is relevant right now? That works until the underlying knowledge changes. A customer contract gets updated. A project owner changes. A policy is revised. A previous fact may no longer be true, but simply overwriting it means the system loses the history behind that change. Utopia handles this with a bitemporal knowledge graph. Each fact can track both when it was true in the real world and when the system learned about it. When something changes, the old fact is preserved instead of silently disappearing. That means an agent can reason about questions like: • What is true now? • What was true three months ago? • When did this information change? • What evidence was the conclusion based on? The graph is also ontology-aware, so documents are represented as entities, facts, and relationships instead of only chunks and embeddings. That gives the system more structure for reasoning across relationships, resolving entities, detecting conflicting facts, and deriving new information through explicit rules. Key capabilities: • Bitemporal knowledge graph for tracking how facts change over time • Provenance on facts so agents can trace where information came from • Conflict detection instead of silently overwriting contradictory information • Ontology-based reasoning across entities, relationships, and derived facts • Hybrid retrieval across full-text search, vector search, and graph traversal • MCP and agentic RAG support for exposing the knowledge layer directly to agents The interesting part is that this turns the knowledge base into more than a retrieval system. Instead of only finding relevant information, an agent can reason over what changed, what is still valid, how facts are connected, and where each conclusion came from. 100% open source. I've shared the GitHub repo in the comments!

Sumanth

16,653 views • 1 month ago

LLM Artifacts Connected to Andrej Karpathy's LLM Knowledge base idea, I've been building out a fun way to generate dynamic artifacts from these knowledge bases with the goal of discovering and revealing meaningful and deeper insights. LLM KBs are hard to consume for humans, as I think they are more built for agents. So the question is, what form would be useful for humans to take actions and make important decisions? That's what I am trying to figure out with these artifacts. The artifact example shows a pulse on HN discussions around AI-related stories. The insights can go deeper, of course, but this is already super fun and thought-provoking, like some of my favorite podcasts. The format and depth matter a lot. The aggregation skills of agents are outstanding if you tune the prompts and skill carefully. I built this artifact generator in a few minutes through an agent skill, but I feel like there are so many ways that LLM-generated information can be used and consumed. Like generating deeper insights and analysis, and things that are just not feasible for humans today. The generated artifact (including its data and design) serves as reusable templates or can be updated in real-time via auomations, which is something I am also working on. It is truly an insane way to monitor and track information. Better than a newsletter. Better than newspapers. There is something about this that gets me really excited about the future of AI agents for knowledge generation and discovery. Lots of hidden gems everywhere just waiting to be discovered and acted on if the information is presented correctly. This is not perfect. The format, style/prose can be improved, but this is easy to customize via skill. You can personalize it to your liking. I feel like these dynamic artifacts are going to emerge as a strong new medium to stay on the cutting edge of things, both for agents and humans. My target is research, of course. This was just a basic example. Besides animation, I am also targeting other components like voice, videos, images, slides, etc. This space is full of opportunities to explore. Skill for this coming soon.
0:18

LLM Artifacts Connected to Andrej Karpathy's LLM Knowledge base idea, I've been building out a fun way to generate dynamic artifacts from these knowledge bases with the goal of discovering and revealing meaningful and deeper insights. LLM KBs are hard to consume for humans, as I think they are more built for agents. So the question is, what form would be useful for humans to take actions and make important decisions? That's what I am trying to figure out with these artifacts. The artifact example shows a pulse on HN discussions around AI-related stories. The insights can go deeper, of course, but this is already super fun and thought-provoking, like some of my favorite podcasts. The format and depth matter a lot. The aggregation skills of agents are outstanding if you tune the prompts and skill carefully. I built this artifact generator in a few minutes through an agent skill, but I feel like there are so many ways that LLM-generated information can be used and consumed. Like generating deeper insights and analysis, and things that are just not feasible for humans today. The generated artifact (including its data and design) serves as reusable templates or can be updated in real-time via auomations, which is something I am also working on. It is truly an insane way to monitor and track information. Better than a newsletter. Better than newspapers. There is something about this that gets me really excited about the future of AI agents for knowledge generation and discovery. Lots of hidden gems everywhere just waiting to be discovered and acted on if the information is presented correctly. This is not perfect. The format, style/prose can be improved, but this is easy to customize via skill. You can personalize it to your liking. I feel like these dynamic artifacts are going to emerge as a strong new medium to stay on the cutting edge of things, both for agents and humans. My target is research, of course. This was just a basic example. Besides animation, I am also targeting other components like voice, videos, images, slides, etc. This space is full of opportunities to explore. Skill for this coming soon.

elvis

31,346 views • 5 months ago

Claude Cowork now has a free, 100% local competitor 🤯 Rowboat connects to your Gmail and meeting notes, builds a knowledge graph of your work, and acts on it. → Voice-enabled → Works with any LLM (local or hosted) → MCP tool extensibility → Background agents + web search → Obsidian-compatible Markdown vault 14.3k GitHub stars. 100% open-source.
0:13

Claude Cowork now has a free, 100% local competitor 🤯 Rowboat connects to your Gmail and meeting notes, builds a knowledge graph of your work, and acts on it. → Voice-enabled → Works with any LLM (local or hosted) → MCP tool extensibility → Background agents + web search → Obsidian-compatible Markdown vault 14.3k GitHub stars. 100% open-source.

Alvaro Cintas

42,472 views • 4 months ago

New Core Wallet 🔺 feature alert! Users can now purchase L1 tokens with fiat in Core with Halliday . - Open Core web ( - Connect a wallet - Navigate to the Command Center and select the Buy tab - Select Halliday - Select the L1 and token and click Continue to Halliday For further instructions, please check out our support article: Have any questions? Please reach out to us on the knowledge base, reply below, or send us a DM! 📩
0:19

New Core Wallet 🔺 feature alert! Users can now purchase L1 tokens with fiat in Core with Halliday . - Open Core web ( - Connect a wallet - Navigate to the Command Center and select the Buy tab - Select Halliday - Select the L1 and token and click Continue to Halliday For further instructions, please check out our support article: Have any questions? Please reach out to us on the knowledge base, reply below, or send us a DM! 📩

Avalanche Support 🔺

30,322 views • 1 year ago

BUILD KARPATHY'S SECOND BRAIN WITH CLAUDE OPUS 5 + OBSIDIAN Andrej Karpathy (OpenAI co-founder) shared an architecture that turns Claude into a persistent second brain not just a basic chat window how it works: > point Claude Code at an Obsidian vault folder > drop articles, PDFs, or video transcripts into raw > Claude reads them, updates summaries, cross-references everything > the knowledge base compounds like interest, never resets on a new chat the setup: > install create a local vault folder > open it in Claude Code, paste Karpathy's wiki prompt > > let the agent build raw, wiki, and CLAUDE.md folders > drop any file into raw, tell it to ingest > ask questions, get compiled summaries back this skips rag overhead entirely. your vault stays organized on its own run ingest on a schedule and it's loop engineering: sense a new file, plan, write, verify, repeat how do you manage your local knowledge base?
0:11

BUILD KARPATHY'S SECOND BRAIN WITH CLAUDE OPUS 5 + OBSIDIAN Andrej Karpathy (OpenAI co-founder) shared an architecture that turns Claude into a persistent second brain not just a basic chat window how it works: > point Claude Code at an Obsidian vault folder > drop articles, PDFs, or video transcripts into raw > Claude reads them, updates summaries, cross-references everything > the knowledge base compounds like interest, never resets on a new chat the setup: > install create a local vault folder > open it in Claude Code, paste Karpathy's wiki prompt > > let the agent build raw, wiki, and CLAUDE.md folders > drop any file into raw, tell it to ingest > ask questions, get compiled summaries back this skips rag overhead entirely. your vault stays organized on its own run ingest on a schedule and it's loop engineering: sense a new file, plan, write, verify, repeat how do you manage your local knowledge base?

Mr. Buzzoni

15,883 views • 1 month ago

Not only do our Agents live + connect across your apps and workflows (Traders, Polymarket Degens, etc) But they can stream, and crossover between any Unreal Engine game (with context). Should we open the plugin to all Solana Solanagaming games? The future of AI is Lucid
0:15

Not only do our Agents live + connect across your apps and workflows (Traders, Polymarket Degens, etc) But they can stream, and crossover between any Unreal Engine game (with context). Should we open the plugin to all Solana Solanagaming games? The future of AI is Lucid

Lucid - Internet of AI (IoAI)

87,928 views • 10 months ago

day 23 of forking Paperclip today i added knowledge bases for projects and you company. based on Andrej Karpathy idea below. added a 'system chores' and 'agent chores' to manage memory. after each heartbeat run memories get added ('agent chores') and every 4 hours memeries get managed. This is in a db with an API for all agents to use and is seperated form the agents memeroes which they get at instantiation time.
0:17

day 23 of forking Paperclip today i added knowledge bases for projects and you company. based on Andrej Karpathy idea below. added a 'system chores' and 'agent chores' to manage memory. after each heartbeat run memories get added ('agent chores') and every 4 hours memeries get managed. This is in a db with an API for all agents to use and is seperated form the agents memeroes which they get at instantiation time.

Michael Houghton 🐺

18,188 views • 6 months ago

A two-person team with agents now out-ships a company of 20, but few can tell you how. The workflows live inside a couple hundred minds. We talk to them daily, and today we're unlocking their brains. Introducing cyber•OS: the open knowledge base for building AI-native.
0:12

A two-person team with agents now out-ships a company of 20, but few can tell you how. The workflows live inside a couple hundred minds. We talk to them daily, and today we're unlocking their brains. Introducing cyber•OS: the open knowledge base for building AI-native.

cyber•Fund

17,089 views • 2 months ago

Building a personal knowledge base for my agents is increasingly where I spend my time these days. Like Andrej Karpathy, I also use Obsidian for my MD vaults. What's different in my approach is that I curate research papers on a daily basis and have actually tuned a Skill for months to find high-signal, relevant papers. I was reviewing and curating papers manually for some time, but now it's all automated as it has gotten so good at capturing what I consider the best of the best. There are so many papers these days, so this is a big deal. You all get to benefit from that with the papers I feature in my timeline and on DAIR.AI. The papers are indexed using tobi lutke qmd cli tool (all of it in markdown files along with useful metadata). So good for semantic search and surfacing insights, unlike anything out there. I am a visual person, so I then started to experiment with how to leverage this personal knowledge base of research papers inside my new interactive artifact generator (mcp tools inside my agent orchestrator system). The result is what you see in the clip. 100s of papers with all sorts of insights visualized. I keep track of research papers daily, so believe me when I tell you that this system is absolutely insane at surfacing insights. This is the result of months of tinkering on how to index research and leverage agent automations for wikification and robust documentation. But this is just the beginning. The visual artifact (which is interactive too) can be changed dynamically as I please. I can prompt my agent to throw any data at it. I can add different views to the data. Different interactions. I feel like this is the most personalized research system I have ever built and used, and it's not even close. The knowledge that the agents are able to surface from this basic setup is already extremely useful as I experiment with new agentic engineering concepts. I feel like this knowledge layer and the higher-level ones I am working on will allow me to maximize other automation tools like autoresearch. The research is only as good as the research questions. And the research questions are only as good as the insights the agents have access to. Where I am spending time now is on how to make this more actionable. I am obsessed about the search problem here. The automations, autoresearch, ralph research loop (I built one months ago) are easier to build but are only as good as what you feed them. Work in progress. More updates soon. Back to building.
0:18

Building a personal knowledge base for my agents is increasingly where I spend my time these days. Like Andrej Karpathy, I also use Obsidian for my MD vaults. What's different in my approach is that I curate research papers on a daily basis and have actually tuned a Skill for months to find high-signal, relevant papers. I was reviewing and curating papers manually for some time, but now it's all automated as it has gotten so good at capturing what I consider the best of the best. There are so many papers these days, so this is a big deal. You all get to benefit from that with the papers I feature in my timeline and on DAIR.AI. The papers are indexed using tobi lutke qmd cli tool (all of it in markdown files along with useful metadata). So good for semantic search and surfacing insights, unlike anything out there. I am a visual person, so I then started to experiment with how to leverage this personal knowledge base of research papers inside my new interactive artifact generator (mcp tools inside my agent orchestrator system). The result is what you see in the clip. 100s of papers with all sorts of insights visualized. I keep track of research papers daily, so believe me when I tell you that this system is absolutely insane at surfacing insights. This is the result of months of tinkering on how to index research and leverage agent automations for wikification and robust documentation. But this is just the beginning. The visual artifact (which is interactive too) can be changed dynamically as I please. I can prompt my agent to throw any data at it. I can add different views to the data. Different interactions. I feel like this is the most personalized research system I have ever built and used, and it's not even close. The knowledge that the agents are able to surface from this basic setup is already extremely useful as I experiment with new agentic engineering concepts. I feel like this knowledge layer and the higher-level ones I am working on will allow me to maximize other automation tools like autoresearch. The research is only as good as the research questions. And the research questions are only as good as the insights the agents have access to. Where I am spending time now is on how to make this more actionable. I am obsessed about the search problem here. The automations, autoresearch, ralph research loop (I built one months ago) are easier to build but are only as good as what you feed them. Work in progress. More updates soon. Back to building.

elvis

467,887 views • 6 months ago

This is the best AI agent-first notes app I've found. It's called . It has the potential to be a productized version of Karpathy's "LLM Wiki" knowledge bases. Here's what I did: 1. Imported "Learning, Fast and Slow" a Continual Learning paper 2. Asked OpenKnowledge to create a visual explainer 3. Read the explainer and had Claude explain to me 4. Created a new section of my own understanding 5. Saved the durable version in my Obsidian vault because it's markdown Free and open-source. Absolutely incredible learning tool.
0:14

This is the best AI agent-first notes app I've found. It's called . It has the potential to be a productized version of Karpathy's "LLM Wiki" knowledge bases. Here's what I did: 1. Imported "Learning, Fast and Slow" a Continual Learning paper 2. Asked OpenKnowledge to create a visual explainer 3. Read the explainer and had Claude explain to me 4. Created a new section of my own understanding 5. Saved the durable version in my Obsidian vault because it's markdown Free and open-source. Absolutely incredible learning tool.

Dan McAteer

17,326 views • 3 months ago

Carotid injury during transsphenoidal surgery is a dreaded event for neurosurgeons. Preoperative knowledge of the anatomy, essential intraopertive tools (Doppler) and a methodical, deliberate action plan by the surgical team is necessary to avoid and mitigate this morbid surgical complication. Thanks to Michael Oh MD Baxter International and Stryker Neurosurgical for allowing us to set up a successful and realistic arterial injury simulation for our amazing residents at UC Irvine Neurosurgery. Skull base surgery remains the ultimate team sport and in a time of crisis, your team must come together 🫶🏽
0:11

Carotid injury during transsphenoidal surgery is a dreaded event for neurosurgeons. Preoperative knowledge of the anatomy, essential intraopertive tools (Doppler) and a methodical, deliberate action plan by the surgical team is necessary to avoid and mitigate this morbid surgical complication. Thanks to Michael Oh MD Baxter International and Stryker Neurosurgical for allowing us to set up a successful and realistic arterial injury simulation for our amazing residents at UC Irvine Neurosurgery. Skull base surgery remains the ultimate team sport and in a time of crisis, your team must come together 🫶🏽

Ahmed Mohyeldin MD PhD

14,270 views • 2 years ago

I just built my own wiki generator plugin for my agents. My agents can now generate wikis for anything I ask. One of my favorite wikis is called PaperWiki. This is a great example of what Andrej Karpathy describes. It uses obsidian vaults to organize papers, retrieve LLM-generated summaries, diagrams, and other advanced views for paper exploration. When Obsidian UI is not enough, I use my own artifact generator inside my agent orchestrator (see clip for example). This allows my agents to build any kind of view or exploration feature that I need. The papers are all curated with automations and several rules/patterns I have manually built over the years. On the surface, this looks basic. But behind the scenes, there are advanced search capabilities, connections, metadata, derived data, and other interesting bits of information that are extremely useful for my research agents. This is mostly built for agents. The artifact preview is just a high-level way to validate and quickly assess the quality of the wiki, suggest improvements, and it's also great for research. I use tobi lutke's qmd for all search capabilities. Everything is markdown. The summaries and even the diagrams. The wiki updates on its own based on several automations I have optimized over the past couple of weeks. The wiki grows and self-improves based on several requirements important for my research use cases. This is as personalized as it gets. There is nothing like it out there. And I use my research expertise to continue improving it over time. This is a vanilla wiki. There are so many things I want to build on top of this. Different aggregations, views, artifacts, etc. All to help automate more of my research work and accelerate productivity. I think the biggest leverage here is how powerful this could be for discovery and experimentation. One of my goals is to use it to find deeper connections and insights that would otherwise elude the top human researchers and use those to generate interesting new hypotheses and research experiments. That way, my agents can use autoresearch to explore research ideas at the frontier. Stay tuned for more.
0:16

I just built my own wiki generator plugin for my agents. My agents can now generate wikis for anything I ask. One of my favorite wikis is called PaperWiki. This is a great example of what Andrej Karpathy describes. It uses obsidian vaults to organize papers, retrieve LLM-generated summaries, diagrams, and other advanced views for paper exploration. When Obsidian UI is not enough, I use my own artifact generator inside my agent orchestrator (see clip for example). This allows my agents to build any kind of view or exploration feature that I need. The papers are all curated with automations and several rules/patterns I have manually built over the years. On the surface, this looks basic. But behind the scenes, there are advanced search capabilities, connections, metadata, derived data, and other interesting bits of information that are extremely useful for my research agents. This is mostly built for agents. The artifact preview is just a high-level way to validate and quickly assess the quality of the wiki, suggest improvements, and it's also great for research. I use tobi lutke's qmd for all search capabilities. Everything is markdown. The summaries and even the diagrams. The wiki updates on its own based on several automations I have optimized over the past couple of weeks. The wiki grows and self-improves based on several requirements important for my research use cases. This is as personalized as it gets. There is nothing like it out there. And I use my research expertise to continue improving it over time. This is a vanilla wiki. There are so many things I want to build on top of this. Different aggregations, views, artifacts, etc. All to help automate more of my research work and accelerate productivity. I think the biggest leverage here is how powerful this could be for discovery and experimentation. One of my goals is to use it to find deeper connections and insights that would otherwise elude the top human researchers and use those to generate interesting new hypotheses and research experiments. That way, my agents can use autoresearch to explore research ideas at the frontier. Stay tuned for more.

elvis

67,308 views • 6 months ago

Scientific progress does not fail because knowledge is absent. It slows in the interval between knowledge and application. The impediments lie less in discovery than in the structures that mediate it: governance, coordination, and the organizational inertia of collective work. The BioAgent Fleet is designed to intervene at this level. Each agent processes the overwhelming flow of scientific literature, inscribes structured insights into a decentralized knowledge graph, evaluates claims against benchmarks, and initiates experimental tasks in cloud-based laboratories. Considered separately, these agents appear as small units of computation. Considered together, they form an emergent architecture of cognition, accelerating the translation from data to hypothesis to validation. Their function is infrastructural, almost invisible, yet decisive. Without them, discoveries remain fragmented and inert. With them, knowledge acquires the velocity required to cross the gap between potential and realization. The next transformation in science will not be marked solely by singular breakthroughs. It will emerge from a new capacity to coordinate distributed intelligences into a coherent, accelerating system.
0:18

Scientific progress does not fail because knowledge is absent. It slows in the interval between knowledge and application. The impediments lie less in discovery than in the structures that mediate it: governance, coordination, and the organizational inertia of collective work. The BioAgent Fleet is designed to intervene at this level. Each agent processes the overwhelming flow of scientific literature, inscribes structured insights into a decentralized knowledge graph, evaluates claims against benchmarks, and initiates experimental tasks in cloud-based laboratories. Considered separately, these agents appear as small units of computation. Considered together, they form an emergent architecture of cognition, accelerating the translation from data to hypothesis to validation. Their function is infrastructural, almost invisible, yet decisive. Without them, discoveries remain fragmented and inert. With them, knowledge acquires the velocity required to cross the gap between potential and realization. The next transformation in science will not be marked solely by singular breakthroughs. It will emerge from a new capacity to coordinate distributed intelligences into a coherent, accelerating system.

Bio Protocol

14,761 views • 1 year ago

V8 DKG Launches Now: A New Dawn for AI in 2025🌟 As 2024 draws to a close, we're excited to announce the immediate launch of V8 Decentralized Knowledge Graph (DKG)! This monumental release is set to redefine AI's capabilities as we step into 2025. What Does V8 Bring to the Table? 🧠Decentralized AI: AI agents can now leverage a 'collective memory' at internet scale, drawing from a shared, yet sovereign, knowledge base. This means AI can provide more contextual, coherent, and accurate interactions without compromising data integrity or privacy. 🚀Unmatched Scalability: With the capability to handle billions of Knowledge Assets, V8 DKG sets the stage for AI to grow and learn in ways we've only imagined, supporting everything from decentralized science to industry 4.0. 🔐Trust and Integrity: With integrated decentralized Retrieval Augmented Generation (dRAG), V8 DKG promotes AI that's more accurate, less biased, and inherently trustworthy. How to V8👇 To update your node from V6 to V8, delegate your TRAC utility tokens, and learn more about creating, connecting and owning your Knowledge Assets, make sure to thoroughly read the following documentation: 👉 With V8 DKG launch, you may now access the new: V8 Explorer👉 AND Staking Dashboard 👉 You may now also participate in V8 Staking Security Bounty by delegating new TRAC stake and report your findings. Read more: 👉 The V8 Staking Security Bounty will importantly contribute to the so-called tuning phase of V8 DKG launch (V8.0 to V8.1). Let's break records, as we usher in a new era of Internet Scale OriginTrail!
0:15

V8 DKG Launches Now: A New Dawn for AI in 2025🌟 As 2024 draws to a close, we're excited to announce the immediate launch of V8 Decentralized Knowledge Graph (DKG)! This monumental release is set to redefine AI's capabilities as we step into 2025. What Does V8 Bring to the Table? 🧠Decentralized AI: AI agents can now leverage a 'collective memory' at internet scale, drawing from a shared, yet sovereign, knowledge base. This means AI can provide more contextual, coherent, and accurate interactions without compromising data integrity or privacy. 🚀Unmatched Scalability: With the capability to handle billions of Knowledge Assets, V8 DKG sets the stage for AI to grow and learn in ways we've only imagined, supporting everything from decentralized science to industry 4.0. 🔐Trust and Integrity: With integrated decentralized Retrieval Augmented Generation (dRAG), V8 DKG promotes AI that's more accurate, less biased, and inherently trustworthy. How to V8👇 To update your node from V6 to V8, delegate your TRAC utility tokens, and learn more about creating, connecting and owning your Knowledge Assets, make sure to thoroughly read the following documentation: 👉 With V8 DKG launch, you may now access the new: V8 Explorer👉 AND Staking Dashboard 👉 You may now also participate in V8 Staking Security Bounty by delegating new TRAC stake and report your findings. Read more: 👉 The V8 Staking Security Bounty will importantly contribute to the so-called tuning phase of V8 DKG launch (V8.0 to V8.1). Let's break records, as we usher in a new era of Internet Scale OriginTrail!

OriginTrail

561,451 views • 1 year ago

Today we're introducing Slite as the first self-maintaining Knowledge Base Your wiki docs go outdated everyday, and your agents depend on them for your most ambitious workflows. Slite monitors your docs' accuracy from all other work tools (slack, jira, linear, codebase, etc) while you sleep and updates them. It even directly talks to your AI agents to give them accurate context without burning their context window or tool calls. You've been trying to build this 'company brain' for months now with hacky MVPs This is the final version of what you need, already built to be collaborative, headless, and secure. Check it out and HMU if you need this for your team, I'll be running personal onboardings for the next few days!
0:12

Today we're introducing Slite as the first self-maintaining Knowledge Base Your wiki docs go outdated everyday, and your agents depend on them for your most ambitious workflows. Slite monitors your docs' accuracy from all other work tools (slack, jira, linear, codebase, etc) while you sleep and updates them. It even directly talks to your AI agents to give them accurate context without burning their context window or tool calls. You've been trying to build this 'company brain' for months now with hacky MVPs This is the final version of what you need, already built to be collaborative, headless, and secure. Check it out and HMU if you need this for your team, I'll be running personal onboardings for the next few days!

Christophe Pasquier

18,325 views • 4 months ago