Skip to content
Tech News
← Back to articles

Your File System Is Already A Graph Database

read original get Neo4j Graph Database → more articles
Why This Matters

This article highlights how existing file systems, especially those using markdown and wikilinks, inherently function as graph databases, enabling seamless integration with large language models (LLMs) for knowledge management. This approach simplifies the creation of personal and team knowledge bases without the need for specialized database systems, making it accessible and efficient for both developers and everyday users. Leveraging familiar tools like file systems and markdown files can significantly enhance productivity and information retrieval in the tech industry.

Key Takeaways

<-- home

Apr 4, 2026

Karpathy recently posted about using LLMs to build personal knowledge bases — collecting raw sources into a directory, having an LLM “compile” them into a wiki of interlinked markdown files, and viewing the whole thing in Obsidian. He followed it up with an “idea file,” a gist you can hand to your agent so it builds the system for you.

This is a great idea, I’ve been doing some form of this for over a decade. My Staff Eng co-host @davidnoelromas reached out after the tweet to ask for more details on how I’ve been using obsidian and AI. This an expanded version of what I told him.

I’ve collected possibly too many markdown files.

find . -type f | wc -l 52447

That’s my obsidian vault, and I use it with AI everyday without a special database, or a vector store, or a RAG pipeline. It’s merely files on disk.

The problem this actually solves

Think about the context you carry around in your head for your job. The history of decisions on a project. What you discussed with your manager three months ago. The Slack thread where the team landed on an approach. The Google Doc someone shared in a meeting you half-remember. The slowly evolving understanding of how a system works that lives across fifteen people’s heads and nowhere else.

Now think about what happens when you need to produce something from all that context. A design doc. A perf packet. A project handoff. An onboarding guide for a new team member. You spend hours reassembling context from Slack, docs, emails, your own memory, and you still miss things.

... continue reading