31–40 of 199 posts
Earlier quoted context omitted.
are you linux or windows? if linux, which distro? Electron support for distros varies so input is appreciated.
I recommend taking a look at appimages or flatpak within Linux if you wish to do so and if you do appimage, try to take an older system within a VM from my understanding as then you wouldn't have issues of glibc which I have sometimes heard. I'd be interested to help if that is of your interest.
Earlier quoted context omitted.
Since Obsidian is just markdown, you can just open an Obsidian vault with OpenKnowledge. We made it so that most Obsidian syntax is supported, like wikilinks. For Notion, we don't have a migration tool, but you can try the export to markdown approach. Recommend trying it to get a feel, and if are looking to migrate and facing friction let me know details.
Obsidian is a lot more than "just markdown" though. For example, with the appropriate plugins like dataview and charts, it's possible to create dashboards, lists, and tables that update automatically based on data elements present in documents or documents themselves. I use it to have views over my to-do lists (daily routine items, tasks that are overdue, upcoming tasks, etc), make dashboards, and show lists of docum…
I don't understand how Obsidian, a collection of markdown files, isn't already AI friendly. It's hard for me to imagine a more AI-friendly but still usable way to organize your notes.
Earlier quoted context omitted.
What we did to go "beyond" is build in skills and an MCP server into the app, and auto-install those into e.g. Claude, Codex, and Cursor formats. Also added a web viewer so that e.g. Claude Desktop can open up the editor directly within it's embedded web viewer.
Why not build skills and an MCP for markdown or obsidian? I'm using both at present and it's fine, bit would like to understand the differentiating factor here.
Making the skills/MCP specific to OpenKnowledge allows us to optimize experiences like that.
I don't understand how Obsidian, a collection of markdown files, isn't already AI friendly. It's hard for me to imagine a more AI-friendly but still usable way to organize your notes.
This. I just open the Obsidian folder (aka "vault") in VS Code and BOOM, it is AI friendly. I just hack on the .md files like I would code with Copilot.
Our goal was you wouldn't need a separate IDE and to work well with the coding agent desktop apps.
But alas -- markdown files on your local machine is indeed the way for being AI friendly.
I don't understand how Obsidian, a collection of markdown files, isn't already AI friendly. It's hard for me to imagine a more AI-friendly but still usable way to organize your notes.
What we did to go "beyond" is build in skills and an MCP server into the app, and auto-install those into e.g. Claude, Codex, and Cursor formats. Also added a web viewer so that e.g. Claude Desktop can open up the editor directly within it's embedded web viewer.
I use Obsidian as a persistent context store and knowledge graph (..loosely defined, i.e. link/back-link) for both Claude Code and Hermes, while also using it to generate live Wiki pages for working documentation. The native replication and the Git integrations work well keeping it all synchronized across multiple harnesses, as well. I use the native MCP server mentioned above, plus just letting the agent work with the markdown files directly.
That said, having built out all of this manually I'm excited to try out something that addresses much of this out of the box. I'd also be curious about the integration with Hermes/OpenClaw/etc.
Earlier quoted context omitted.
What we did to go "beyond" is build in skills and an MCP server into the app, and auto-install those into e.g. Claude, Codex, and Cursor formats. Also added a web viewer so that e.g. Claude Desktop can open up the editor directly within it's embedded web viewer.
There is at least one MCP server in Obsidian's community plugins, plus the REST API access capability which is already addressed in several open source MCP plugins. I use Obsidian as a persistent context store and knowledge graph (..loosely defined, i.e. link/back-link) for both Claude Code and Hermes, while also using it to generate live Wiki pages for working documentation. The native replication and the Git integr…
Large inspiration for OpenKnowledge was providing these flows out of the box.
We'll prioritize Hermes/OpenClaw guides next.
Feel free to drop me any feedback as you try it out - @nickgomez on X.
Having built-in AI integration without relying on sketchy plugins would be the cherry on top (although, seriously missing the option to connect with any openai-compatible LLM provider like someone else mentioned here).
Seems like this might almost offer exactly that? I'll have to try it out...