fh2378

[Muhammad Ayan @socialwithaayan]

🚨 BREAKING: Someone just built the exact tool Andrej Karpathy said someone should build.

48 hours after Karpathy posted his LLM Knowledge Bases workflow, this showed up on GitHub.

It's called Graphify. One command. Any folder. Full knowledge graph.

Point it at any folder. Run /graphify inside Claude Code. Walk away.

Here is what comes out the other side:

-> A navigable knowledge graph of everything in that folder
-> An Obsidian vault with backlinked articles
-> A wiki that starts at index. md and maps every concept cluster
-> Plain English Q&A over your entire codebase or research folder

You can ask it things like:

"What calls this function?"
"What connects these two concepts?"
"What are the most important nodes in this project?"

No vector database. No setup. No config files.

The token efficiency number is what got me:

71.5x fewer tokens per query compared to reading raw files.

That is not a small improvement. That is a completely different paradigm for how AI agents reason over large codebases.

What it supports:

-> Code in 13 programming languages
-> PDFs
-> Images via Claude Vision
-> Markdown files

Install in one line:

pip install graphify && graphify install

Then type /graphify in Claude Code and point it at anything.

Karpathy asked. Someone delivered in 48 hours.

That is the pace of 2026.

Open Source. Free.

[Jaden思考日志 @Jaden_riku]

https://t.co/i1xzQ9wRCA

[Andrej Karpathy @karpathy]

LLM Knowledge Bases

Something I'm finding very useful recently: using LLMs to build personal knowledge bases for various topics of research interest. In this way, a large fraction of my recent token throughput is going less into manipulating code, and more into manipulating knowledge (stored as markdown and images). The latest LLMs are quite good at it. So:

Data ingest:
I index source documents (articles, papers, repos, datasets, images, etc.) into a raw/ directory, then I use an LLM to incrementally "compile" a wiki, which is just a collection of .md files in a directory structure. The wiki includes summaries of all the data in raw/, backlinks, and then it categorizes data into concepts, writes articles for them, and links them all. To convert web articles into .md files I like to use the Obsidian Web Clipper extension, and then I also use a hotkey to download all the related images to local so that my LLM can easily reference them.

IDE:
I use Obsidian as the IDE "frontend" where I can view the raw data, the the compiled wiki, and the derived visualizations. Important to note that the LLM writes and maintains all of the data of the wiki, I rarely touch it directly. I've played with a few Obsidian plugins to render and view data in other ways (e.g. Marp for slides).

Q&A:
Where things get interesting is that once your wiki is big enough (e.g. mine on some recent research is ~100 articles and ~400K words), you can ask your LLM agent all kinds of complex questions against the wiki, and it will go off, research the answers, etc. I thought I had to reach for fancy RAG, but the LLM has been pretty good about auto-maintaining index files and brief summaries of all the documents and it reads all the important related data fairly easily at this ~small scale.

Output:
Instead of getting answers in text/terminal, I like to have it render markdown files for me, or slide shows (Marp format), or matplotlib images, all of which I then view again in Obsidian. You can imagine many other visual output formats depending on the query. Often, I end up "filing" the outputs back into the wiki to enhance it for further queries. So my own explorations and queries always "add up" in the knowledge base.

Linting:
I've run some LLM "health checks" over the wiki to e.g. find inconsistent data, impute missing data (with web searchers), find interesting connections for new article candidates, etc., to incrementally clean up the wiki and enhance its overall data integrity. The LLMs are quite good at suggesting further questions to ask and look into.

Extra tools:
I find myself developing additional tools to process the data, e.g. I vibe coded a small and naive search engine over the wiki, which I both use directly (in a web ui), but more often I want to hand it off to an LLM via CLI as a tool for larger queries.

Further explorations:
As the repo grows, the natural desire is to also think about synthetic data generation + finetuning to have your LLM "know" the data in its weights instead of just context windows.

TLDR: raw data from a given number of sources is collected, then compiled by an LLM into a .md wiki, then operated on by various CLIs by the LLM to do Q&A and to incrementally enhance the wiki, and all of it viewable in Obsidian. You rarely ever write or edit the wiki manually, it's the domain of the LLM. I think there is room here for an incredible new product instead of a hacky collection of scripts.

[Hoody @HoodyLiu]

https://t.co/PryG99IgXq

[fh2378 @fh2378]

@liamgallagher pussy dare you send it again, FAKE

[fh2378 @fh2378]

@icarusart_ai 最爱的当然是3000万的淑女啦

[OdailyNews @OdailyChina]

第一届Odaily 线上加密狂欢节正式开幕，知名艺术家宋婷的展馆【诗人漫步-找寻遗失的记忆碎片】已上线，��接：https://t.co/A9lMO5G9x3
关注我们以及@icarusart_ai @Song11Ting，点赞、转发、评论本条推特说出本展馆你最喜爱的参展作品，@icarusart_ai将随机抽选两位朋友送出限量版NFT一枚，快来参与吧

[OdailyNews @OdailyChina]

第一届Odaily 线上加密狂欢节正式开幕，知名艺术家宋婷的展馆【诗人漫步-找寻遗失的记忆碎片】已上线，链接：https://t.co/A9lMO5G9x3
关注我们以及@icarusart_ai @Song11Ting��点赞、转发、评论本条推特说出本展馆你最喜爱的参展作品，@icarusart_ai将随机抽选两位朋友送出限量版NFT一枚，快来参与吧

[fh2378 @fh2378]

@mmm989866 怎么联系？

[fh2378 @fh2378]

@JesseKellyDC any evidence? troller

[fh2378 @fh2378]

@RyanAFournier Trump lied and tried to hide it too. Why dont you propose arrest him?