Karpathy's 400,000-word AI wiki exposes a gap nobody is talking about

Everyone is talking about Karpathy's LLM knowledge base. 16 million views in a few weeks. But nobody is naming the actual problem it reveals.

Karpathy built a personal wiki, roughly 100 articles and 400,000 words, compiled entirely by an AI from his raw research docs. He didn't write a single word of it. It's one of the most compelling demos of what personal AI knowledge infrastructure can look like.

But here's the problem: The wiki lives on his machine. Every time he opens a different AI tool, it knows nothing about it.

That's not a Karpathy problem. That's everyone's problem.

Some other people like Allie Miller built a "context vault," structured summary docs she feeds into Claude to avoid re-explaining herself every session. Teams are using Notion as a memory layer. Developers are writing custom scripts to sync context across tools. Some are setting up github wikis, while some are using Obsidian to set up local markdown files.

All brilliant. All manual. All solving the same root failure: AI has no durable, portable sense of who you are.

Every time you open Claude, Cursor, ChatGPT, or whatever ships next month, it starts from zero. There is no standard for "this is who I am" that travels with you. The burden of continuity falls entirely on the user.

Some will point to Claude's memory feature or ChatGPT's memory. These are genuine steps forward. But they are per-platform, opaque, and you don't own them. Switch tools and you start over. They are not solving the
portability problem. They are each building their own silo of you.

The real issue is that context continuity is being treated as a feature when it is actually infrastructure.

Features get built per-product. Infrastructure sits beneath products. What's missing is a memory layer that sits above any individual tool. One canonical store of your context, preferences, and knowledge that you own, control, and selectively grant any AI permission to read. Not stored by Anthropic. Not stored by OpenAI. Portable across the fragmented AI landscape.

A year ago the coordination problem here would have been enormous. Getting AI providers to query an external context layer would have required deals, standards negotiations, and a lot of waiting.

MCP changed that. MCP (Model Context Protocol) is an open standard that lets AI tools query external data sources directly. Any AI tool that supports MCP can already read from an external context server, no special agreements with providers required. The infrastructure exists. What has been missing is someone building the right thing on top of it: a user-owned, canonical context store that any MCP-compatible AI can read with your permission. For example, with the AICF MCP Server, you could not only read but directly add, edit, delete, organize your cross-platform memories from within the AI chats.

Our vision: One memory. Every AI. Owned by you.

p.s. we have a lifetime deal going on AppSumo which will end this month: https://appsumo.8odi.net/m4n0da