I have been a long-time user of Obsidian, but this is my first time registering on the forum because I am both excited and apprehensive about the current state of Obsidian. Even before the AI era, its powerful openness and intelligent interaction logic made me deeply fall in love with it. As a researcher, my primary need is to record plain text notes, sometimes inserting handwritten content or images, and Obsidian meets these needs perfectly. Even when I need to write text in formats other than Markdown, the plugin marketplace offers various powerful text-editing enhancements that provide an experience with a lower learning curve but no less—or even superior to—Vim. For example, one of my common use cases is writing LaTeX in Obsidian and compiling it directly with a LaTeX compiler that supports .md files.
What pleasantly surprised me is how seamlessly Obsidian has integrated with AI in this new era. If before the AI era I would modestly say Obsidian was one of the best personal note-taking apps in the world, today I can confidently say it is the best. Its Markdown content serves as the best retrieval source for AI, its canvas feature feels like a workflow stage tailor-made for AI years in advance, and its bidirectional linking natively enhances AI’s understanding of the knowledge base like a knowledge graph. All these foundational advantages of the AI era are quickly realized as usable features thanks to its open and vibrant plugin ecosystem. I have already joyfully downloaded several AI plugins that significantly improve my note-taking experience and can’t put them down. This is precisely what excites me and one of the reasons I registered for this forum to write this post.
However, another reason driving me to register is my unease. Obsidian is undoubtedly the best among pre-AI-era note-taking apps in embracing AI, almost solidifying its position as the best personal note-taking software today. But its AI ecosystem is not perfect—there are still current issues and future concerns. The most immediate problem is that, despite Obsidian having the best foundational advantages for AI, the official team hasn’t packaged these features for us directly. Everything still requires plugin developers and users to implement them manually. For example, with AI plugins featuring RAG capabilities, each one I install requires rebuilding the database using embedding models, which undoubtedly leads to significant resource redundancy and waste.
Additionally, different third-party plugins offer varying levels of support for various model providers. Users with only a few provider APIs may struggle to ensure the next plugin they download will work properly. Even for those with access to multiple providers, manually configuring each plugin’s settings adds substantial overhead to the user experience. I believe the official team should address these issues with better services:
- Provide unified database access support: Since different AI plugins have varying database requirements, the official solution shouldn’t be a single database service but rather a “database hub” where users can create a single database for all plugins to share or multiple dedicated databases for specific plugins.
- Offer unified LLM API management: The specifics of this feature don’t need much elaboration, as there are already many examples in the market.
These are the immediate issues I think need addressing. As for the longer-term outlook, I am optimistic, but I also see potentially fatal challenges that may be hard to resolve. Before the AI era, Obsidian thrived thanks to its open plugin ecosystem, becoming one of the best note-taking apps and quickly adapting to the AI era. Though I’m not a professional developer, I suspect that maintaining compatibility with existing third-party plugins could become a burden for Obsidian’s next leap forward. Currently, all its advantages are relative to pre-AI-era note-taking apps, but what might dethrone it won’t necessarily be its past competitors—it could be future challengers. Newer apps, natively designed for AI from the ground up, could absorb all of Obsidian’s strengths while being lighter, more efficient, and unencumbered by legacy support. However, because Obsidian must maintain compatibility with its plugin ecosystem, making major architectural changes won’t be easy—like a large ship struggling to turn. This could prevent it from making crucial adjustments, leading to failure in the distant future. While I recognize this problem, I must admit I don’t have concrete suggestions, as I’m just a user more familiar with the experience side rather than technical implementation. Still, I hope the Obsidian team takes this seriously and begins strategic planning early. I want to continue happily editing my notes, papers, and code in Obsidian years from now without needing to migrate to another platform.
Since this is my first time posting here, I’m unsure if my thoughts overlap with others’. If so, moderators are welcome to delete this post.
English is not my first language, so I appreciate everyone who took the time to read this.
Here’s to hoping Obsidian delivers an even better experience in the future!