Field note · The AI second brain
Tiago Forte named the second brain. Andrej Karpathy handed it to the AI. Garry Tan ran it across thousands of files. Between them they proved something real: an AI that maintains your knowledge for you works. And every single version still expects you to be a software engineer. Clone the repo, write the config, wire the API keys, schedule the agents, keep the vault synced and debug it when something goes wrong. Maxy gives you the same outcome with none of that work, on a graph that outperforms a folder of text files.
A short lineage
In under a decade the "second brain" went from a productivity method to a pattern an agent maintains for you. Obsidian made local markdown its home throughout. The idea is proven; credit where it's due.
2017 →
Tiago Forte
Coined Building a Second Brain. Capture, organise, distil, express: your notes as an external mind.
2026 →
Andrej Karpathy
The "LLM Wiki": markdown maintained by the agent, keeping the index in context rather than retrieving it on demand.
2026 →
Garry Tan
Operationalised it. GBrain & Gstack run the wiki across thousands of files. "The agent runs while I sleep."
Now
The builders
Open kits (e.g. obsidian-second-brain) add self-rewriting pages, contradiction sweeps, nightly consolidation.
The catch
Read the setup guide for any of them and the friction is the same. The intelligence is real; the on-ramp is a developer's. Before the second brain does a thing for you, you do all of this:
They proved the idea. They also proved the price of admission: months of a developer's weekends. Maxy exists to remove that cost. The store you end up with is better than a folder of markdown files.
Maxy, axis one
There is nothing to clone, configure or debug. Maxy arrives installed and running on your own server: the graph, the agents, the ingestion engines and the channels are all assembled. It runs inside your flat Claude subscription, so there are no metered API charges for research or transcription. The second brain that took those builders months of setup is, for you, already on.
Maxy, axis two
A markdown vault is a good single-user, local, read-mostly store. Each of those qualifiers breaks the moment the store is shared, searched constantly and held to account. A flat file needs a vector database, a search engine and a graph library added by hand to match what Maxy has built in.
| What you actually need | Markdown vault | Maxy graph |
|---|---|---|
| Find by meaning, not keyword | Add an external vector DB | Vector + keyword search, fused in one query |
| Typed relationships (who founded, who attended) | Wikilinks are untyped | Validated edge types, queryable both ways |
| No duplicates, no contradictions | By convention, by hand | Enforced at the moment of writing |
| Many people, one knowledge base | One vault per person | Tenant isolation in the database itself |
| Private vs. customer-facing answers | Two separate vaults | One store, scope-aware retrieval |
| Undo, audit, GDPR erase & export | Deletion is destructive | Soft-delete, grace period, full export |
| "What did we believe last March?" | Frontmatter gymnastics | Living summary beside an immutable timeline |
The verdict
Forte, Karpathy and Tan showed the AI second brain works. They also showed it costs a developer's months to stand one up and keep it alive. Maxy removes that cost. What you end up running is not a folder of text files; it is an ontological knowledge graph: shared, searchable by meaning, audited, and yours.
Keep an Obsidian vault you love? Bring it. Maxy ingests it on day one. Markdown is a fine place to think. A graph you did not have to build is a better place to store what you know.