The Rise of AI-Powered Second Brains
Everyone is suddenly building a second brain. Karpathy's LLM wiki pattern went viral, and half of X is now hand-wiring Obsidian to Claude Code so an agent maintains their notes for them.
The idea is beautiful: stop making your AI re-read raw notes on every question. Let it build a wiki that compounds. As Karpathy put it, "LLMs don't get bored, they don't forget to update a cross-reference (backlinks), and can touch 15 files in one pass."
But if you start doing it manually, it becomes a project in itself. You wire up the vault, the agents, the schedules, the integrations, and then you babysit all of it.
So I sat down with Arjun Maheswaran, who actually built the open source version of this, and we broke down what it looks like when the whole thing already works out of the box.
It just crossed 15K stars on GitHub.
Think Claude's desktop app, open source, with two things layered on top:
→ A work brain: background agents index your emails, meetings, and notes into a living knowledge graph that updates itself as you work.
→ Work surfaces: chat is not the best interface for real work, so you get an email client, a meeting note taker, a browser, and a code mode where you and the AI actually collaborate.
The part that got me: a customer email comes in asking for a product change, a background agent triages it, spins up Claude Code in its own worktree, and the feature is written before you are back at your desk.
Bring your existing Obsidian vault, connect Slack, X, and Fireflies, and let it run your day.
Here's what we covered in this session:
- what is Rowboat (an open source ai co-worker)
- the second brain (a knowledge graph of your work)
- bringing your existing Obsidian vault in
- meetings and automatic note taking
- connecting Slack, X and other sources
- background agents that run your day
- code mode (Claude Code and Codex)
- demo: from an email to written code
- guardrails: approvals and agent workspaces
- scheduling agents on a cron
- the browser work surface (browser use)
- wrapping up: automating your whole day
This post is mostly accurate, but it combines verifiable facts, product descriptions, opinions, and at least one strong marketing claim.
Fact check
"Andrej Karpathy: 'There's room for an incredible new product in the AI second brain space.'"
✅ Accurate.
Karpathy has publicly expressed this idea while discussing LLM-powered personal knowledge systems and "second brain" products.
"Karpathy's LLM wiki pattern went viral."
✅ Generally accurate.
His LLM wiki concept received widespread attention across X and the AI developer community.
"Half of X is now..."
🟡 Hyperbole.
This is rhetorical rather than factual.
"Stop making your AI re-read raw notes...build a wiki that compounds."
✅ Accurate conceptually.
Structured knowledge bases are a common pattern for improving retrieval and long-term organization.
"LLMs don't get bored...can touch 15 files in one pass."
✅ Accurate as a quotation/paraphrase if attributed correctly to Karpathy.
"I sat down with Arjun Maheswaran..."
✅ Personal claim.
Assuming this interview occurred, it's not something that can be independently fact-checked here.
"It just crossed 15K stars on GitHub."
🟡 Needs current verification.
GitHub star counts change frequently.
"A work brain...living knowledge graph..."
🟡 Mostly accurate as a product description.
If Rowboat markets this architecture, it's fair. Whether it's literally a knowledge graph depends on its implementation.
"Background agents index your emails, meetings, and notes..."
✅ Plausible.
Many AI workspace tools perform this type of indexing.
"Email client, meeting note taker, browser, code mode..."
✅ Likely accurate if these are actual Rowboat features.
"A customer email...background agent...Claude Code...feature is written before you are back at your desk."
🟡 Marketing/demo scenario.
Technically possible with automation, but it shouldn't be interpreted as a guaranteed real-world workflow.
"Bring your existing Obsidian vault, connect Slack, X and Fireflies..."
✅ Accurate if those integrations exist.
Session topics
✅ Accurate if they reflect the actual presentation.
Overall verdict
Accuracy: 8.5/10
The post accurately describes:
Karpathy's "second brain" vision.
The growing trend toward AI-maintained knowledge bases.
The general capabilities of AI coworker platforms.
The weaker points are:
Dynamic GitHub star count.
"Half of X..."
The autonomous coding-from-email example, which is better viewed as a product demo than a typical workflow.
Real vs Fluff
🟢 80% Real | 🟡 20% Fluff
Real (80%)
Karpathy's second-brain ideas.
LLM wiki concept.
Obsidian integration trend.
AI knowledge management.
Background agents.
Workspace integrations.
Fluff (20%)
"Half of X..."
GitHub star count (time-sensitive).
Fully autonomous "email to completed feature" scenario presented as a representative workflow.
Some product marketing language around "run your day."
Overall, the technical direction is sound, but the post mixes concrete features with aspirational product messaging.