Martijn Verbove@verboveProduct · #1

I've been building something for myself called Memex. It's a native macOS app that basically replaces Finder for my personal knowledge base, with an AI agent doing the librarian work. The idea is stolen from Karpathy's LLM-wiki pattern. You don't organize your notes yourself. You just dump raw stuff in a vault: PDFs, screenshots, web captures, whole conversations, entire folders. An LLM maintains the wiki for you. It writes the topic pages, links things together, merges duplicates, and cites every claim back to its source. Under the hood it's deliberately boring. The vault is just markdown on disk. Raw sources never change, and the wiki on top is plain files with wikilinks. No database, no lock-in. The agent is Claude Code running headless inside the vault. Ask it a question and you get an answer with citations. Give it a command and it creates and reorganizes pages while you watch it work in the chat rail. The best part: feeding it is automatic. Memex runs a local interceptor on your Mac that catches your AI conversations. Every Claude Code session gets forwarded the moment it ends, and Claude and ChatGPT chats flow in through the same endpoint. Talk to an AI about something and it's in your wiki minutes later. It also pulls data in through MCPs on a schedule. Gmail, meeting transcripts, whatever has an MCP server. You set the cadence, the agent syncs it in and works it into the wiki. Every source gets a number when it comes in. Every wiki page ends with a table of its sources, and every claim has a citation you can click through to the original file. So the wiki keeps evolving but you never lose track of where anything came from. If anyone wants to try it, comment or DM me.

AI knowledge base system architecture explained