Obsidian vs Claude Code: Do You Still Need It?

Obsidian vs Claude Code: an Obsidian vault is just Markdown files in a folder, so to an AI it looks like any folder. Here is what Claude Code replaces and how…
People often ask me what I think of Obsidian. The short answer: I have it installed, but I barely open it. Not because it is a bad tool, but because for the way I work it is not a tool I need. This piece lays out how I decide whether notes belong in Obsidian or in a plain local folder driven by Claude Code, and why I landed where I did.
One more piece of context. Among the AI engineers whose work I follow most closely, I have almost never seen anyone using Obsidian. I don’t read that as a judgment on the app. I read it as a signal that once AI sits in the middle of your workflow, the job a note app used to do changes shape.
Obsidian notes are just Markdown files
Start with the fact that settles most of the argument. An Obsidian vault is Markdown files, and the data sits directly in a folder on your computer. The notes are not pulled into a proprietary cloud; they are plain text on your own disk.
That matters because it separates two things people usually bundle together: the data itself, and the doorway you use to reach the data. Obsidian sells you a doorway. The data was already just files.
It also means the stakes of the decision are lower than they feel. When people ask “which note tool should I commit to,” they are often really asking “where will I be trapped in three years.” If the contents are Markdown in a folder, that question mostly dissolves, and what is left is a much smaller question about daily comfort.
To an AI, a vault is not a special place
Point an AI at an Obsidian vault, then point it at an ordinary notes folder. It sees the same thing both times: a pile of Markdown files. There is no hidden structure that makes a vault smarter to read. So the expectation that “if I keep it in Obsidian, the AI will handle it better” does not hold. Handling it well is a capability on the AI side, and it has nothing to do with where the file lives.
Once that is clear, the question changes shape. It stops being “should I use Obsidian” and becomes “do I need this particular doorway.”
What Claude Code replaces
The reason I stopped opening Obsidian is that most of what it was selling me, I now get by asking in plain language.
- Tracing related notes. “Show me every note that mentions Customer A” returns it in one shot. No links to maintain, no tag taxonomy to design up front.
- Cross-note search and aggregation. Plain language is more flexible than hunting for a plugin and configuring it. When I want a different cut, I just ask differently.
- Summarizing and organizing. Obsidian cannot do this at all. Turning a pile of notes into something readable is work that only the AI side can do.
The third one is the one that matters. The first two are just “what I could do over there, I can also do over here.” The third is a capability the note app never had, and it flips the premise of the whole exercise. The value of notes is not in accumulating them; it is in being able to use them. When the using side gets dramatically stronger, elaborate machinery on the accumulating side matters less.
You stop paying the structure tax
Power-using a note app means spending time on structure: which tag, which link, which folder. That work is a prepayment against a future search. If you can find things later by describing what you want, you can skip most of the prepayment. For me the biggest change was not retrieval speed — it was having fewer decisions to make at the moment of writing. Capture got cheaper, so I capture more.
Where Obsidian still earns its place
There are still cases where a dedicated doorway is worth having. I can think of three:
- You want to re-read notes on your phone.
- You want to look at them in a clean, well-formatted view.
- You want to drop in a single line, fast.
What those three share is that they are about the human side of the loop. Not how the AI reads your data, but how you write it and how you look at it. Catching a thought while you are moving around, or skimming related notes with your own eyes before a meeting, is a real need, and a purpose-built doorway serves it well.
If you don’t do those three things, Claude Code plus a local folder is enough. If you write at your desk and search from your desk, a second doorway buys you nothing. Note that none of the three is about intelligence — they are about reach and comfort. That is a useful test for any tool in this category: if its pitch is intelligence, check whether the model is already doing that part for you.
How to decide between Obsidian and a local folder
Here is the order I would work through.
- Decide what you actually want. Accumulate, retrieve, or synthesize — the answer differs for each.
- List where you write and where you read. Desktop only? A folder is fine. Phone in the mix? You need a doorway.
- Check whether your retrieval pattern is fixed. The same roll-up every week favors a built-in tool feature. A different angle every time favors plain language.
- Check who is doing the synthesis. If a person is summarizing and reorganizing by hand, that is the part to hand over.
- When in doubt, start with the simpler setup. Because the contents are just Markdown files, adding a doorway later is easier than peeling one off.
Run that list and “which tool is best” mostly collapses into “where is my work actually stuck.” Before you build a comparison table, try writing the stuck point in one line. If you can’t, no tool choice will fix it.
Why the question arrives as a tool name in Japan
A note on the Japanese context, since that is where most of these questions reach me. They almost always arrive as a product name, and “what do you think of Obsidian?” is exactly that shape. It is not a bad instinct, but it is a hard question to answer well, because a tool-name question invites a yes-or-no verdict.
Start from the task instead and you get an answer tied to your own work. If you are the person pushing AI adoption inside a Japanese company, the first question to ask your team is not “which tool should we roll out” but “where does your work stall today.” That single question usually reveals whether what is missing is a tool or a procedure.
I think the same holds for overseas AI and tech companies explaining a product to a Japanese audience. In my experience, “here is which task changes, and how” lands better than a feature list. In the Obsidian case, the line that travels is not “you can traverse related notes” — it is “you no longer have to design a tag system.” Say which existing step of the reader’s workflow you replace before you say what you are better at.
Taking this back to your own team
If you are the one deciding where notes and meeting records live, map three things first. Where does the data sit? How many doorways reach it? Who is doing the searching, and who is doing the summarizing? Write those down and it becomes clear whether what you are missing is a tool or a procedure.
For me the answer was to keep the data in a local folder and hand both searching and summarizing to the AI. I don’t think that is the only right answer. If you have found uses or advantages for Obsidian beyond the ones above, I would genuinely like to hear them.
FAQ
Should I stop using Obsidian?
This is not a verdict on the tool. In my own workflow its necessity is low, so I barely open it. If re-reading on your phone, looking at a clean view, or dropping in a single line quickly matters to you, it still earns its place.
Can Claude Code replace Obsidian?
For tracing related notes and doing cross-note search or aggregation, asking in plain language is enough. Summarizing and organizing is something Obsidian cannot do at all. Mobile reading and presentation are a separate question, so decide based on whether you need those.
Where does Obsidian store my notes?
An Obsidian vault is just Markdown files, sitting in a folder on your computer. That is why, to an AI, an Obsidian vault and an ordinary folder look exactly the same.
Based on a post on XOriginal post ↗