The System Was Never Broken. The User Was.

Obsidian is a well-built tool. Local-first. Markdown-native. Fast. Infinitely extensible. There is nothing technically wrong with it, and this article isn't going to pretend otherwise.

The problem is who it was designed for. Not you, specifically. A fictional version of you. The one who reviews notes every morning, maintains clean consistent tagging, builds out backlinks with intention, and synthesizes insights from the vault on a weekly basis.

That person doesn't exist in large numbers. Or more precisely: if that person exists, they don't need this article.

Everyone else builds a vault, uses it enthusiastically for a few weeks, then gradually stops retrieving anything. The notes are there. The system technically works. But it requires a discipline most people don't sustain, and the design doesn't account for that.

What Actually Happens to Vaults

Most Obsidian vaults follow the same lifecycle. You set one up with genuine enthusiasm. You design a folder structure. You pick a tagging taxonomy. You read some PKM blog posts and adopt a methodology. PARA, maybe. Something Zettelkasten-adjacent. You start capturing.

For a while, it feels productive. Notes are going in. The graph view shows connections forming. You feel like someone who has their thinking organized.

Then retrieval becomes the problem. Not capture. Retrieval. You know you wrote something about a specific topic three months ago, but you can't remember what you called it, and the tag you used that day isn't the tag you'd search for today. The note might as well not exist. The vault becomes a knowledge graveyard: full of things you captured and will never surface again, because surfacing them requires you to remember you captured them in the first place.

The system didn't fail in the technical sense. The maintenance model failed. It required too much from you, too consistently, for too little visible return. That's not a motivation problem. It's a design problem.

PKM systems tend to get redesigned rather than used. You reorganize when you should be writing. You refine tags when you should be capturing ideas. The meta-work of maintaining the system crowds out the actual work the system was supposed to support.

The Design Shift AI Makes Possible

Here is the reframe that changes the entire calculus: stop building your second brain for you. Build it for your AI agent.

This idea, articulated clearly in the AI Cliff newsletter on Substack, is less obvious than it sounds. It's not just "add an AI plugin to your PKM setup." It's a essentially different design philosophy about who the primary user of the system actually is.

A human-first system needs to be browsable, well-tagged, and logically organized. Humans retrieve by category and memory cue. They need folder structures they can scan and tags they can recognize. An AI-first system needs to be readable and rich in context. Agents retrieve by semantic search and relevance scoring. Those are different requirements that produce different architectures.

An agent doesn't need you to remember you captured something. It doesn't care whether your folders are clean or your tags are consistent. It searches, connects, and synthesizes on demand. Your only job in an AI-first system is to capture. Retrieval, organization, and synthesis become the agent's responsibility.

That's a meaningful division of labor. It removes the maintenance burden that kills every human-first PKM system eventually.

The shift also changes what good capture looks like. In a human-first system, a good note is organized, tagged, and linked. In an AI-first system, a good note is honest, specific, and datestamped. Context over taxonomy. Substance over structure.

What People Are Actually Moving To

The tools gaining traction in this space are worth knowing. None of them are obvious one-to-one replacements for Obsidian in the traditional sense.

Khoj is an open-source AI agent that runs locally or in the cloud and reasons across your notes without requiring manual organization or input on your part. You point it at your files. It handles the rest. No tagging required. No folder structure to maintain.

Files.md takes the opposite approach: plain files, minimal interface, maximum data ownership. The core pitch is simplicity over maintenance overhead. Less structure to maintain means less structure to abandon when motivation dips.

The Claude Code plus Obsidian hybrid is more interesting than either of those standalone options. Claude Code runs as an active background agent that ingests and processes your existing vault continuously. Your Obsidian notes don't move. They stay where they are, in the format they're already in. But they stop being static. The vault becomes active input material rather than a filing system you're supposed to browse on your own initiative.

That last option matters specifically because it addresses the main objection Obsidian defenders raise: local-first data sovereignty. Your files stay yours. They stay local. You just stop being the primary user of them. The agent is.

The Case for Keeping Obsidian Anyway

Obsidian's defenders have real arguments worth taking seriously. The local-first, offline Markdown architecture gives you something cloud AI tools genuinely cannot: ownership of your data with no vendor dependency and no subscription risk. That's not a minor consideration if you've been building a knowledge base for years.

The backlink and graph structure also creates metadata that AI agents can work with more effectively than unstructured flat text. A vault with deliberate connections is richer input than a folder of unlinked notes. The structure you built for human browsing turns out to be meaningful for semantic reasoning too, even if it was built for a different purpose.

There's also a growing plugin ecosystem pushing toward the agent-layer model from inside Obsidian. Copilot for Obsidian, Graphify, and similar tools are adding AI reasoning layers without requiring you to migrate anywhere. For users with large, reasonably well-structured vaults, this path is probably the most sensible. Abandon the browsing habit. Keep the data. Let the plugins do the synthesis work.

The argument here isn't that Obsidian is the wrong tool. It's that the way most people use Obsidian is misaligned with how people actually behave when there's no external accountability keeping them to the maintenance schedule.

What to Do With the Vault You Already Have

If you have an existing Obsidian vault full of notes you haven't meaningfully touched in months, the answer is not to delete it. That would be a waste of whatever you did capture.

The answer is to stop treating it as a system that requires your ongoing maintenance and start treating it as a corpus that an agent can read. Those are different relationships with the same set of files.

Stop building new taxonomies. Stop reorganizing folders. Stop feeling guilty about the notes you haven't reviewed or the backlinks you meant to add. The discipline-dependent parts of PKM are exactly where every human-first system eventually breaks down. AI agents don't have a discipline problem. They have no feelings about the gap between your intentions and your behavior.

Point an agent at what you have. Khoj, Claude Code, a simple RAG setup against your Markdown files. Your existing notes are probably more useful as raw input material than as a browsable archive you're theoretically supposed to curate on a regular schedule.

For new captures, simplify aggressively. Plain text. Minimal friction. Dates, not taxonomies. A sentence or two of context, not full atomic notes with carefully formatted headers. Let the agent figure out what connects to what. That's the job you've been trying to do yourself, and it's a job agents do faster and without complaining about it.

The vault you built for yourself may actually be more valuable once you stop being its primary user.

Your AI doesn't need a perfect filing system.

It just needs something to read.