Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Introducing Wikiwise: an open-source Mac app for managing your own Karpathy-style LLM wiki. Set up a new wiki in a few clicks: all you need is Wikiwise + your agent. It's infinitely customizable, just markdown/html under the hood, and one click to share your wiki publicly. Here's how it...

96,906 Aufrufe • vor 7 Monaten •via X (Twitter)

42 Kommentare

Profilbild von Tristan
Tristanvor 7 Monaten

You can install Wikiwise here: View the source on Github: View the Wiki I created in the video here: or the other wiki I mentioned here: LMK what you think :)

Profilbild von Tristan
Tristanvor 7 Monaten

hahahah yesssss that was the inspo, thanks to @deadly_onion

Profilbild von Bartos
Bartosvor 7 Monaten

Thanks for sharing 🙏🏼

Profilbild von lukas
lukasvor 7 Monaten

this is awesome, can’t wait to give it a spin. putting those readwise highlights to good use

Profilbild von Tristan
Tristanvor 7 Monaten

exactly! so much you can do with them

Profilbild von lukas
lukasvor 6 Monaten

do you have a favorite use case?

Profilbild von Jeff Lee
Jeff Leevor 7 Monaten

Love this! Building the same thing with

Profilbild von Tristan
Tristanvor 7 Monaten

haha cool, from performative notes to performative wikis 😂

Profilbild von Jeff Lee
Jeff Leevor 7 Monaten

Lol The goal is to have people learn more from their notes via wiki. Lets hope wikis wont be just sitting there

Profilbild von Ranjan
Ranjanvor 7 Monaten

this is fascinating - have been using Cowork over Obsidian but basically this is what i'm trying to do! and more integrated

Profilbild von Tristan
Tristanvor 7 Monaten

nice! i can imagine cowork is great for this kind of stuff :) you could probably point cowork at a wikiwise directory too instead of a terminal agent!

Profilbild von blakeinu0
blakeinu0vor 7 Monaten

can we make a pf and send a donation to your github? would love to support this bro.

Profilbild von Matt Mullenweg
Matt Mullenwegvor 6 Monaten

THAT IS SO COOL!!!!!!

Profilbild von Gordon McCreight
Gordon McCreightvor 7 Monaten

This looks great! I'm building something focused purely on the publishing side at I find LLM notes most useful when carefully assimilated into my own densely-linked notes. Publishing meaningful extracts from those connected notes requires a lot of care.

Profilbild von Thiago Ghisi
Thiago Ghisivor 7 Monaten

@readwise this is awesome Tristan! Loving how much cool stuff you are shipping

Profilbild von Tristan
Tristanvor 7 Monaten

@readwise Thanks! This was just an experiment at our team hackathon but i think the direction is super interesting!

Profilbild von pimpernel
pimpernelvor 7 Monaten

Looks great, just need to buy a Mac!!

Profilbild von Tristan
Tristanvor 7 Monaten

😭 "claude make a windows wikiwise app. make no mistakes"

Profilbild von pimpernel
pimpernelvor 7 Monaten

🤣🙏

Profilbild von Manthan Shah
Manthan Shahvor 6 Monaten

Thank you - this is the only acceptable Obsidian alternative I will support!

Profilbild von Roberto Salem
Roberto Salemvor 7 Monaten

Super cool! Really curious what’s the intended use and the applicability of the graph view experience ?

Profilbild von Tristan
Tristanvor 7 Monaten

You can use it for any kind of research, notetaking, learning, etc. I'd recommend checking out the quoted tweet from @karpathy , it's a way of implementing his "LLM Knowledge Base"

Profilbild von Roberto Salem
Roberto Salemvor 7 Monaten

I wrote more about this below, but I still don’t see graph view itself as the real day-to-day value. Visualizing connections is cool to play with. The real unlock is when an LLM can use the underlying KG, traverse those relationships, and turn them into useful output🤔

Profilbild von Tristan
Tristanvor 7 Monaten

@karpathy ohhh you just mean the graph view yourself? i don't think it's a big deal in terms of these wikis, it's just a fun way to get an overview of the connections and pages the LLM can already traverse the links so it can do that!

Profilbild von Roberto Salem
Roberto Salemvor 7 Monaten

@karpathy Right exactly. What feels compelling to me isn’t graph view by itself, but graph view behind the output: you work with the LLM on something in canvas, and as it evolves, you can see the knowledge map it’s pulling from and connecting through.

Profilbild von Royce Branning
Royce Branningvor 6 Monaten

COOOOOOK

Profilbild von jessepinkman
jessepinkmanvor 7 Monaten

built a simple npx too scffold your obsidian vault & qmd - npx claude-second-brain - thats it -

Profilbild von Tristan
Tristanvor 7 Monaten

that's really cool! but obsidian on its own: * is not open source, nor customizable enough * is cluttered -- does a lot of things and has a lot of functionality/core plugins you don't need * publishing is pretty brutal UX + $$$

Profilbild von jessepinkman
jessepinkmanvor 7 Monaten

No arguments there. Obsidian distribution and brand recognition is unbeatable. Everyone in tech has tried it at some point in time. So felt like if the plumbing was faster/low effort with familiar tools, people might be more likely to give it a shot

Profilbild von PageIndex
PageIndexvor 7 Monaten

We just open-sourced OpenKB: Open LLM Knowledge Base In addition to Andrej's original design, OpenKB can scale to long PDFs and multi-modality.

Profilbild von Crypto Value Labs
Crypto Value Labsvor 6 Monaten

I will put all my personal files into a second-brain app some random dudes vibe-coded last Sunday night? NYET!!!

Profilbild von Maksim Siadura
Maksim Siaduravor 6 Monaten

Look cool but I know people for them less complicated matters, and Andrei did his way really good for it

Profilbild von Jaswinder Singh
Jaswinder Singhvor 6 Monaten

Read AGENTS.md. The "edit 2-3 related pages" rule in the ingest skill got me thinking. Curious if it scales past 50ish pages, or if the agent starts grabbing the obvious links and missing subtler ones. Going to spin one up this weekend and see. Have you seen recall fall off as wikis grow, or does lint usually catch it?

Profilbild von Tristan
Tristanvor 6 Monaten

Good question! I haven't seen any recall issues, but I also haven't gone past 100 pages. To me that goes from a topic-specific wiki (which karpathy originally described) to a general wiki... also a cool concept but a bit of a different problem. That being said, I think it's pretty trivial to just extend the AGENTS.md for your wiki to scale better.. and of course can add some things like qmd if needed!

Profilbild von Jaswinder Singh
Jaswinder Singhvor 6 Monaten

nice, makes sense. I was thinking who does topic clustering for readwise but just saw the import-readwise skill and that readwise cli handles it. clean.

Profilbild von web3nomad.eth | atypica.ai
web3nomad.eth | atypica.aivor 6 Monaten

"one click to share publicly" is the interesting design choice here — most wiki patterns assume private knowledge compilation. making it public-first changes the incentive: you curate differently when you know others will read it. that tension might actually improve knowledge quality.

Profilbild von James
Jamesvor 7 Monaten

how is this compared to llmwiki? I am curious

Profilbild von Tristan
Tristanvor 7 Monaten

You can think of this as an IDE for implementing+browsing+publishing your own llm wiki!

Profilbild von Nostaline
Nostalinevor 6 Monaten

A terminal-bound relic shaped by Andrej Karpathy’s vision hoarding fragments of knowledge like blood in sealed vaults, waiting to be drawn.

Profilbild von Celestin Eiffel
Celestin Eiffelvor 6 Monaten

Something to keep in mind: Claude Code requires a Claude Pro/Max subscription or Anthropic Console API credits because every time you ask it to ingest a file, you are using Anthropic’s high-end cloud computing power.

Profilbild von Kn
Knvor 7 Monaten

This might be the cleanest take yet on Andrej Karpathy’s LLM wiki idea, turning notes into a living system. Saw something similar done by a MIT prof, seems inspired by karpathy:

Profilbild von MrGreen.eth
MrGreen.ethvor 6 Monaten

We've actually made a similar format in terminal based of Karpathy's idea of LLM Knowledge Bases. Give it a spin and let me know what you think

Ähnliche Videos

HERMES AGENT SHIPS WITH A BUNDLED SKILL FOR ANDREJ KARPATHY'S LLM WIKI PATTERN. A SELF-IMPROVING KNOWLEDGE BASE THAT GROWS EVERY TIME YOU FEED IT. mentioned this briefly in the overnight workflow article. here is the full breakdown. what it is: a self-improving knowledge base built as interlinked markdown files. unlike RAG (which rediscovers knowledge from scratch every query), the wiki compiles knowledge once and keeps it current. cross-references stay linked. contradictions get flagged automatically. synthesis reflects everything ingested so far. why this matters for Hermes memory: Hermes built-in memory knows YOU. it remembers your conversations, your preferences, your business context across sessions. but it doesn't know your inbox. or your meeting transcripts. or that article you saved last week. or the expert framework you want it to learn. the LLM Wiki solves that. THE DIVISION OF LABOR human curates sources and directs analysis. agent summarizes, cross-references, files, and maintains consistency. you drop in articles, transcripts, notes. Hermes indexes them, links related concepts, flags contradictions, updates affected pages. your knowledge base grows itself. SETUP IS ONE COMMAND the skill ships with Hermes. enable it. set WIKI_PATH in ~/.hermes/.env: WIKI_PATH=/Users/you/wiki defaults to ~/wiki if unset. then drop anything into it: "index this article into my wiki: [paste URL or text]" Hermes reads it, builds a source page, updates related entries, flags contradictions. THE OBSIDIAN ANGLE set OBSIDIAN_VAULT_PATH to the same directory. now your wiki is visible in Obsidian's graph view. nodes, links, backlinks. all built by Hermes. for headless servers: install obsidian-headless. syncs vaults without a GUI. agent writes from the server, you read on your laptop. THE COMPOUND EFFECT Hermes knows you. the wiki knows your world. combine them and the agent answers questions using BOTH contexts at once. month 1: you explain things twice. month 3: the agent references the wiki on its own. answers get sharper because the knowledge base got sharper. AUTOMATIONS THAT FEED THE WIKI set cron jobs to ingest automatically: "every day at 9am, check Granola for new meetings. add any new transcripts to my wiki under meeting notes." "every morning, scan my Gmail starred items. add anything worth keeping to the wiki." "every week, check arXiv for new papers in [your niche]. summarize and file." your wiki grows while you sleep. Hermes never forgets what gets indexed. THE LIMITATION TO KNOW unlike Hermes memory (which is conversational and lives across sessions), the wiki is a separate knowledge layer. Hermes won't pull from the wiki automatically unless you reference it or save it as a skill. best setup: build an LLM Wiki personality that tells Hermes to consult the wiki when answering strategy questions or domain-specific queries. full HERMES AGENT OVERNIGHT WORKFLOW👇

YanXbt

30,804 Aufrufe • vor 4 Monaten

I still don’t understand why people keep building a Claude second brain by hand when these 10 repos already built the whole system They turn your Claude sessions into a wiki, let Claude read and write your vault from your phone, and one of them comes straight from Obsidian’s own CEO 01 llm-wiki → your Claude Code and Codex sessions become a searchable wiki, with an MCP server to query it 02 llm-wiki-claude-skill → one skill file teaches Claude to ingest sources, answer from them, lint the wiki and compile it into clean pages 03 obsidian-skills → Obsidian’s own CEO teaches Claude how Obsidian really works 04 llm-wiki → a Claude Code plugin with init, ingest, compile, query and lint, where every change is committed to git 05 obsidian-dev-second-brain → your tickets, sprints and project docs live in the vault as notes, and Claude keeps them in sync with the code 06 obsidian-mcp-server → 14 tools to read, write, search and surgically edit notes, tags and frontmatter 07 mcpvault → safe vault access with a read-only mode, and Obsidian doesn’t even need to be running 08 obsidian-claude-code-mcp → connect Claude Code to your open vault with one /ide command 09 obsidian-web-mcp → reach your vault from your phone or any MCP client, with OAuth and a Cloudflare Tunnel 10 obsidian-mcp → a git-backed vault with 18 tools, running locally or on AWS Lambda Nobody is going to build your second brain for you, and every chat you close without one is knowledge thrown away. Bookmark this, pick one repo from 01 to 05 and ingest your first source tonight. A month from now you have a wiki, and everyone who skipped it is still opening a blank chat.

Ryven

10,722 Aufrufe • vor 5 Tagen

This is Farzapedia. I had an LLM take 2,500 entries from my diary, Apple Notes, and some iMessage convos to create a personal Wikipedia for me. It made 400 detailed articles for my friends, my startups, research areas, and even my favorite animes and their impact on me complete with backlinks. But, this Wiki was not built for me! I built it for my agent! The structure of the wiki files and how it's all backlinked is very easily crawlable by any agent + makes it a truly useful knowledge base. I can spin up Claude Code on the wiki and starting at index.md (a catalog of all my articles) the agent does a really good job at drilling into the specific pages on my wiki it needs context on when I have a query. For example, when trying to cook up a new landing page I may ask: "I'm trying to design this landing page for a new idea I have. Please look into the images and films that inspired me recently and give me ideas for new copy and aesthetics". In my diary I kept track of everything from: learnings, people, inspo, interesting links, images. So the agent reads my wiki and pulls up my "Philosophy" articles from notes on a Studio Ghibli documentary, "Competitor" articles with YC companies whose landing pages I screenshotted, and pics of 1970s Beatles merch I saved years ago. And it delivers a great answer. I built a similar system to this a year ago with RAG but it was ass. A knowledge base that lets an agent find what it needs via a file system it actually understands just works better. The most magical thing now is as I add new things to my wiki (articles, images of inspo, meeting notes) the system will likely update 2-3 different articles where it feels that context belongs, or, just creates a new article. It's like this super genius librarian for your brain that's always filing stuff for your perfectly and also let's you easily query the knowledge for tasks useful to you (ex. design, product, writing, etc) and it never gets tired. I might spend next week productizing this, if that's of interest to you DM me + tell me your usecase!

Farza 🇵🇰🇺🇸

2,162,244 Aufrufe • vor 7 Monaten

Here's how I'm running automated content engine in 2 files 1 markdown file = my wiki 1 html file = my dashboard that's the whole stack. [ the architecture, in plain words ]: LLM wiki = a single markdown file holding my audience DNA, 15 tracked creators, every viral topic from the last 30 days HTML artifact = a single page that reads that markdown file AND can trigger my agents the artifact and the agent talk to each other directly the wiki is the shared brain [ what I actually see when I open it at 9am ]: > 5 trending topics ranked by my audience-DNA fit > 3 KOL posts worth quoting today > last week's saved tweets (so I can ride waves that are still warm) > buttons: [draft tweet] [draft QT] [schedule] [log idea] 1. I click "draft tweet" on a topic 2. the artifact pings my agent 3. agent reads the wiki, drafts in MY voice, returns it to the artifact 4. I edit, schedule, done 15 minutes from morning coffee to 3 scheduled posts [ how to build the same in one evening ]: > step 1: dump your domain knowledge into ONE markdown file (audience profile, KOL list, content rules, voice guide, anything an agent would need to do YOUR job) > step 2: ask claude to build an html artifact that reads from that file ("here's my wiki, build me a dashboard with these views") > step 3: add buttons for the actions you do daily (draft, schedule, log, score, search — your workflow, not mine) > step 4: wire each button to call your agent via tool calls (so the artifact and the agent talk directly) the moment your artifact reads your wiki AND triggers your agents.. most SaaS tools you currently pay for quietly become unnecessary dashboards I used to pay $50/month for now sit in a single html file I can rebuild in 20 minutes every "I'll build a SaaS for this" idea you had last year is a 200-line file you write in an afternoon if you want to get the same content engine, just reply "CONTENT" and will send you in DMs later we're going from buying software to owning it.

Ronin

50,427 Aufrufe • vor 6 Monaten

this is f*cking insane. andrej karpathy: "the biggest regret of every engineer in my field right now is every AI conversation they never saved, and in 10 years the ones who started saving in 2024 will be running circles around the rest of us" andrej karpathy, co-founder of openai, pulled 16M views on one idea: stop using AI to write code, use it to build a second brain that remembers every article, pdf, transcript and conversation you ever fed it you point claude code at a folder, drop anything into it, and claude reads it, cross-links it with everything already there, and writes it into a living wiki. your knowledge finally compounds instead of leaking out of your head every friday the stack: → brew install obsidian, mkdir ~/vault, cd ~/vault → run claude in that folder and type "init a knowledge vault with CLAUDE.md as the rules, /raw for sources, /wiki for your pages" → drop any file into /raw (youtube transcript, meeting notes, 400-page pdf, screenshot of a tweet) and type "ingest" → claude writes a wiki page, links it to 5 existing ones automatically, updates CLAUDE.md with any new pattern it noticed about how you think → never open a blank claude chat again. every question goes through the vault, every answer cites your own sources with dates and links 5 minutes to set up. compounding knowledge from that evening forward the ugly part most will scroll past: in 10 years the engineers who started this in 2024 will remember every book, every podcast, every meeting with receipts. you will remember none of them. karpathy already picked which side he is on and you are still not on his full step-by-step is in the article below bookmark this before you waste another monday

mojesko

461,651 Aufrufe • vor 7 Tagen