I’ve been using several different AI plugins in Obsidian, such as Copilot, Smart Connection, and InsightA (developed by myself XD). Each of these plugins requires me to independently configure API keys and select models. Additionally, many plugins support only a limited number of models, very few support local models, and even fewer are compatible with OpenRouter. This setup has become quite cumbersome to manage.
So, why don’t we develop a single plugin where you only need to configure the API key and model once, and then other plugins can utilize this centralized AI configuration? I’m really interested in creating such a plugin myself, but I’m curious why no one else has done it yet. Is there a technical barrier preventing this, or does a plugin like this already exist that I might not be aware of?
I would love to hear your thoughts on this. Has anyone attempted something similar, or are there specific challenges I should consider before diving into development?
It’s a great idea to have a standard AI interface plugin in Obsidian. The current fragmented setup, where each plugin requires separate API key configuration, can be frustrating, especially when managing multiple models. One possible reason why this hasn’t been done yet could be the differences in API structures, authentication methods, and supported models across various services. Some plugins might be optimized for specific LLMs, making standardization tricky. If you develop such a plugin, you could position it as the freecine for AI in Obsidian, a centralized hub where users configure settings once and other plugins pull from it. Compatibility with OpenRouter and local models would be a huge plus.
The previous post made a good point, so I created the 15th standard xd. It’s super easy to use, and I’ve already tried it on my other plugins.
Here’s the ai interface plugin and it’s now under review. It supports multiple providers and models, custom models, endpoints, local llms, etc. Feel free to tell me you guys need anything else.
That’s a great question! Once the plugin is approved, I plan to spread the word on relevant developer forums and communities—such as the Obsidian forum, Reddit, Discord, Twitter, and more. I’ll also reach out directly to developers to let them know about it. If you have any other suggestions for outreach, please share! And if you’re interested, feel free to help out by promoting it to your friends or even incorporating it into your own plugins.