Josh Booy

how a simple llm wiki compares to gbrain second brains are getting popular fast, they're one of the main enablers for ai and agents right now. the context you give an agent is what makes it good two frameworks I've been using are the LLM Wiki and Gbrain. here's how they compare, and how to use both underneath they're the same idea, karpathy's llm wiki: you compile raw sources into linked markdown pages your agent reads, instead of redoing RAG from scratch every time both ingest your sources, build a graph out of them, and answer with citations, so the real question is what's actually different an LLM wiki is just markdown and your agent: > it reads your sources and writes linked pages > you ask a question and it reads those pages to answer > you keep it healthy with a lint pass > there's no database, just files, and one user it works well, and karpathy even points out where it starts to break down: > the synthesis drifts after a lot of updates > the context cost grows as the wiki gets big > a wrong claim can harden into fact over time gbrain is that same wiki with an engine built for those exact problems: > better retrieval, vector plus graph plus a reranker, instead of the agent reading pages > it runs on postgres, so it scales past what you could ever read yourself > a 24/7 loop enriches and fixes the wiki on its own, so there's no manual lint > every answer comes with sources and an honest note on what it doesn't know yet > it's multi-user, with access scoped per person and team when to reach for each: > use an llm wiki for smaller projects, to gather and store the context an agent will use later on. when it grows up, you can ingest it straight into gbrain > use gbrain for the consistent, shared things, a company brain or a client brain, especially once more people are involved so it's not wiki vs brain, it's the same wiki run by you on a small project, versus the same wiki run by an engine at scale for a team start simple, then move to gbrain when you outgrow the files