Andrej Karpathy
AI AgentsThe Karpathy knowledge base and LLM wiki guide — vibe coding, autoresearch, agentic engineering, and LLM deep dives. 37 curated pieces from his blog posts, lectures, and X threads, organized by topic with AI summaries.
About this vault
The complete Karpathy knowledge base and personal AI second brain: vibe coding, autoresearch, agentic engineering, LLM wiki, and LLM deep dives — organized by topic, not just timeline. Covers his April 2026 LLM knowledge base + LLM wiki methodology — the 'compiler analogy' approach that bypasses RAG (16M+ tweet views), his three-folder system (raw → wiki → outputs) for building a self-maintaining personal AI knowledge base, the vibe coding manifesto he coined (now Collins Dictionary's word of the year), his autoresearch framework (21K+ GitHub stars), his 3.5-hour LLM deep dive lectures, and the post-code AI workflow shift from writing code to orchestrating knowledge. Each piece has an AI summary so you can decide what to read in seconds. Auto-synced — new Karpathy content appears here automatically.
Karpathy's Three-Folder LLM Wiki System
Andrej Karpathy's personal AI knowledge base uses three folders that process information in a pipeline. The system bypasses traditional RAG and works with any capable LLM.
- 1. Raw — Unfiltered inputs. Articles, transcripts, X threads, research papers, podcast notes. Everything goes in as-is, timestamped. This is the append-only firehose. No organization, no tags, no pre-interpretation.
- 2. Wiki — Synthesized topic pages. Concepts get their own living file, continuously edited as new raw material lands. The wiki is the map, not the territory — a self-updating mental model per topic, written for future-you.
- 3. Outputs — Finished artifacts published downstream. Essays, tweets, lectures, code, talks. Outputs are what the wiki eventually becomes when an external deadline demands it — the wiki compresses into a public product.
Karpathy describes this as the “post-code AI workflow” — the shift from writing code as the primary creative act to orchestrating knowledge. The canonical pieces on the pattern are in the reading list below.
No articles yet.
Start reading, not hoarding.
Import this vault to Burn 451 and actually read what matters.
New to Burn? See how the read-later app works →
Frequently asked questions
Who is Andrej Karpathy?
Andrej Karpathy is covered in this Burn 451 vault with a focus on ai agents. The Karpathy knowledge base and LLM wiki guide — vibe coding, autoresearch, agentic engineering, and LLM deep dives. 37 curated pieces from his blog posts, lectures, and X threads, organized by topic with AI summaries.
How was the Andrej Karpathy vault curated?
The Andrej Karpathy vault was hand-curated by the Burn 451 editorial team from publicly available essays, blog posts, podcast transcripts, and social threads. Each piece includes an AI-generated summary so readers can triage in seconds. The vault auto-syncs as new content from Andrej Karpathy is published.
How many articles are in the Andrej Karpathy vault?
The Andrej Karpathy vault currently contains 37 curated pieces organized by topic, not chronology. Each article has an AI summary and a direct link to the original source. Items are refreshed hourly through Burn 451's ISR pipeline, so new publications appear within a day.
How do I use this vault with Claude or Cursor?
Install the burn-mcp-server package from npm and connect it to Claude, Cursor, or any MCP-compatible AI tool. The vault becomes queryable as live context — your AI can search, summarize, and cite articles from Andrej Karpathy directly in conversation without manual copy-paste or re-uploading files.
What is Burn 451?
Burn 451 is a read-later app built around a 24-hour burn timer that forces daily triage. Articles you save must be read, vaulted, or released within 24 hours. The Vault layer — including this Andrej Karpathy collection — holds permanent curated reading lists for AI thought leaders, founders, and researchers.
Content attributed to original authors. Burn 451 curates publicly available writing as a reading index. For removal requests, contact @hawking520.