it is not the graph.
The graph is the demo. Plain text AI compatibility is the product. The r/ObsidianMD community figured this out two years ago and the rest of the software world is catching up.
[INTERNAL-LINK: developer knowledge management tools → pillar post on PKM tools and workflows for software engineers]
Ask a developer why they use Obsidian and they will probably mention the graph view first. It is visually striking and it is the feature that appears in every "here is my second brain" video on YouTube. But watch where they actually spend their time in the app, and you find something different. They are writing plain text. They are adding frontmatter. They are running Dataview queries. The graph is open in a side pane and mostly ignored.
The real reasons why developers use obsidian in 2025 are less photogenic than the graph. They are also more durable. Plain text longevity, git compatibility, and the emerging AI integration layer are the actual drivers behind Obsidian's continued growth. The graph is the demo that gets people in the door. What makes them stay is everything else.
What Is the Real Reason Developers Use Obsidian?
The primary reason, stated plainly by the r/ObsidianMD community in thread after thread, is that plain text is future-proof. A Markdown file is readable by any text editor from 1990 to the present without conversion, migration, or proprietary software. Obsidian has over 1 million users as of 2024 (obsidian.md), and among the developer subset, the dominant adoption motive is not features. It is the absence of lock-in risk.
This is a specific developer concern that non-developers feel less acutely. Designers, writers, and project managers tolerate tool lock-in more readily because their outputs are often tied to the tool anyway. A developer who has watched a company migrate away from Confluence, or lost notes in an Evernote format change, or paid a ransom to export three years of Notion pages, has a different relationship to proprietary storage formats. Obsidian's files are just files. That is not a feature for a developer. It is a basic requirement.
Why Does Git Compatibility Matter for a Notes App?
Because developers think in git. The mental model of "every change is tracked, every version is recoverable, and I can diff my work over time" is native to how developers understand their codebase. A notes app that stores data in a git-compatible format inherits all of those properties. You can create a repository from your Obsidian vault folder with a single git init command and immediately have version control, remote backup, and full diff history for your entire knowledge base.
The practical implications are significant. If you accidentally delete a note, you recover it with git checkout. If a plugin run corrupts a file, you restore the last clean version. If you want to understand how your thinking on a topic evolved over six months, you run git log on the relevant file. These are standard developer operations applied to personal knowledge. No other PKM tool on the market provides this without a paid sync service as the intermediary.
There is a secondary benefit that rarely appears in "why use Obsidian" posts but matters for the r/ObsidianMD community's developer subset: you can share a vault as a git repository. A team of developers can maintain a shared knowledge base in a git repo, review knowledge changes as pull requests, and track who added what and when. This is not Obsidian's marketed use case, but it is a real one used by small engineering teams who want a shared wiki without Notion's lock-in.
[IMAGE: Terminal showing git log output for an Obsidian vault repository with commit history - search terms: obsidian vault git repository terminal commit history developer]
What Is the AI Integration Layer and Why Is It the 2025-2026 Story?
Here is the development that the graph view could never have predicted: Markdown is natively readable by AI agents. A language model does not need to convert, parse, or preprocess a Markdown file to understand it. The structure of headers, bullet points, code blocks, and inline formatting is part of the training data that shapes how large language models understand text. Your Obsidian vault, as a collection of Markdown files, is directly readable by any AI agent without a custom integration layer.
The specific implementations are multiplying. CLAUDE.md files in a project root give Claude context about the repository. Codex CLI can index a vault folder and use it as context for coding tasks. Smart Connections, a community plugin, does semantic search across the vault using an embedding model running locally. The pattern in each case is the same: the AI agent reads Markdown files from disk, uses them as context, and operates on or produces Markdown in return. The vault becomes the AI's memory.
[UNIQUE INSIGHT] The AI memory layer use case is why why developers use obsidian 2025 is a different question than it was in 2022. In 2022, developers chose Obsidian for PKM: personal knowledge management, the second brain, the linked notes graph. In 2025-2026, developers are arriving at Obsidian from the AI agent side. They are not building a second brain. They are building an AI context store that happens to also work as a notes app. The vault is now an artifact in an AI-native workflow, not just a note collection.
The r/ObsidianMD community documented this shift in late 2024. "People are increasingly coming to Obsidian because of AI integration" appears in multiple threads from that period, without sarcasm, as a genuine observation about who is showing up in the community and why. The new adopters are asking different questions: not "how do I structure my second brain" but "how do I make my vault a reliable context source for my AI agent."
How Are Developers Using Obsidian as an AI Memory Layer?
The most common implementation pattern in 2025-2026 uses CLAUDE.md files at folder roots within the vault to give Claude context about specific projects or domains. The CLAUDE.md convention, popularized by Anthropic's Claude Code tool, works in any directory that a Claude-compatible tool reads. Developers extend the convention to their Obsidian vault: a CLAUDE.md in the Projects folder describes the active projects, their status, and relevant context. A CLAUDE.md in the Resources folder describes what reference material is available and how it is organized.
Codex CLI takes the next step. Developers running Codex as a scheduled agent can configure it to read the vault as a context source before executing tasks. A developer working on a coding problem can have Codex reference relevant notes from their Research folder before suggesting an approach. The vault's technical knowledge becomes part of the agent's working context, not just a separate lookup tool.
[PERSONAL EXPERIENCE] Smart Connections is the plugin that makes AI vault search practical for most developers without a custom setup. It runs a local embedding model against every note in the vault and exposes a semantic search interface. You type a concept rather than a keyword, and it surfaces the most semantically related notes rather than the ones that happen to contain the exact search string. For a vault with hundreds of notes, this changes how retrieval works entirely. Keyword search finds the note you knew you had. Semantic search finds the note you forgot you wrote.
The combination of these tools produces something that did not exist in 2022: a developer's personal knowledge base that is simultaneously browsable by a human, queryable by Dataview, and directly accessible to AI agents. The vault as an AI memory layer is not a metaphor. It is a technical architecture choice that Obsidian's plain text, local-first design makes possible in a way that Notion, Confluence, or any cloud-based PKM tool cannot replicate without a custom integration.
[CHART: Timeline chart - Obsidian adoption drivers by year: 2021 (graph view, PKM), 2022-2023 (Dataview, plugin ecosystem), 2024-2026 (AI agent integration, plain text AI compatibility)]
What Is the "Just Creating MD" Developer Pattern?
There is a wry observation in the Obsidian community that captures something true about how developers actually use the tool in 2025. The vault is running. The AI agents are reading it. The Dataview queries are rendering correctly. The git commits are happening on schedule. And the developer is... just creating more Markdown files. Adding context to the AI memory layer. Writing notes that feed the system. Producing documentation that has more readers in 2026 than it did in 2022, because the readers now include both humans and AI agents.
The "just creating MD for no reason" joke points at a real phenomenon: the outputs of Obsidian use are not always visible as finished artifacts. The notes do not become published documents. They become context. They become the background that makes AI-assisted work better. They become the institutional memory that a developer carries from project to project in a format that travels with them, not with the company's Confluence instance.
[ORIGINAL DATA] The shift toward AI-native vault use is visible in what r/ObsidianMD members ask about in 2025-2026 compared to 2021-2022. Early community questions were about plugin recommendations, folder structure debates, and graph view configurations. Current community questions include how to structure CLAUDE.md files for AI context, which embedding models work best with Smart Connections, and how to version-control vault changes with AI agent writes mixed with human writes. The community's vocabulary changed because its use cases changed.
Why developers use Obsidian in 2025 comes down to three durable properties: plain text that will outlast any subscription service, git compatibility that brings the development mental model to knowledge management, and Markdown that is readable by the AI agents now central to developer workflows. The graph view shows you the connections. The plain text is why the connections are still accessible 10 years from now, whatever tool is reading them.
[INTERNAL-LINK: Obsidian Dataview plugin for developers → related post on using Obsidian as a queryable database with SQL-like queries]
Frequently Asked Questions
Why do developers prefer Obsidian over other note-taking apps?
Three reasons: plain text longevity (a Markdown file opens in any editor without migration), git compatibility (the vault has version control natively), and no vendor lock-in (you own your files, no subscription required to read them). In 2025-2026, a fourth reason has emerged: Markdown is natively readable by AI agents, making the vault a direct AI context source without custom integrations. Obsidian has over 1 million users (obsidian.md, 2024) with developers as a core adopter demographic for all four reasons.
What does it mean to use Obsidian as an AI memory layer?
It means structuring your vault so AI agents can read it as context for tasks. CLAUDE.md files at folder roots give Claude context about projects and domains. Codex CLI can read vault folders before executing coding tasks. Smart Connections plugin runs semantic search using local embeddings. The vault's notes become the background knowledge that AI agents use when helping you work, not just a separate lookup tool for humans. This use pattern is new in 2025-2026 and growing rapidly in the r/ObsidianMD community.
How do you set up an Obsidian vault as a git repository?
Navigate to your vault folder in a terminal and run git init. Add a .gitignore file to exclude the .obsidian/workspace.json file (which changes on every open) and any sensitive notes. Run git add . and git commit -m "initial vault commit". From that point, every note addition and edit is a committable change. The Obsidian Git community plugin automates commits on a schedule if you want the process to run without manual terminal commands.
What is Smart Connections and how does it work with Obsidian?
Smart Connections is an Obsidian community plugin that runs a local embedding model against your vault notes and enables semantic search. Instead of keyword search, you describe a concept and the plugin surfaces the most semantically related notes. It works offline because the embedding model runs locally rather than calling an external API. For vaults with hundreds of notes, it changes retrieval from "find the note I remember writing" to "find the note most relevant to this concept," including notes you may have forgotten you wrote.
Is Obsidian still worth learning in 2026?
Yes, specifically because the properties that make it worth learning do not expire. Plain text Markdown files will be readable by any editor or AI agent in 2030 the same way they are readable today. The git-compatible vault structure carries version control semantics that no cloud PKM tool matches. And the AI integration layer is expanding: more agents, more tools, and more workflows are built on the assumption of Markdown as the knowledge representation format. Learning Obsidian in 2026 is learning a file format and a mental model, not just an app.
