I've been using my opencode go subscription for Obsidian, saving my Claude sub for actual coding. Any reason why it's limited to Codex, Claude, and Cursor?
Show HN: OpenKnowledge – open source AI-first alternative to Obsidian/Notion
51–60 of 199 posts
Re: Show HN: OpenKnowledge – open source AI-first alternative to Obsidian/Notion
#52Local models should be the first choice in that framing.
Re: Show HN: OpenKnowledge – open source AI-first alternative to Obsidian/Notion
#53Re: Show HN: OpenKnowledge – open source AI-first alternative to Obsidian/Notion
#54You should just integrate with pi.dev, like I did for https://github.com/rcarmo/piclaw (which has replaced Obsidian for me). I too integrated a terminal and a WYSIWYG Markdown editor (as well as plugins for a mindmap, kanban, etc.)
Re: Show HN: OpenKnowledge – open source AI-first alternative to Obsidian/Notion
#55I've been using my opencode go subscription for Obsidian, saving my Claude sub for actual coding. Any reason why it's limited to Codex, Claude, and Cursor?
Re: Show HN: OpenKnowledge – open source AI-first alternative to Obsidian/Notion
#56Nothing personal, but there genuinely ought to be consequences for using "open source" in the context of something like this tied to proprietary AI services. Local models should be the first choice in that framing.
We're looking at OpenCode/Zed next but open to input.
Re: Show HN: OpenKnowledge – open source AI-first alternative to Obsidian/Notion
#57Earlier quoted context omitted.
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…
Right on. We did a lot of the same and then had to deal with coaching everyone on the team how to do also set it up. 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.
Re: Show HN: OpenKnowledge – open source AI-first alternative to Obsidian/Notion
#58Earlier quoted context omitted.
Agree same. We'll look into explicit guides and integrations with Zed // OpenCode as a starting point, they let you choose your model.
Amazing, thanks. I've decided to try daily driving this instead of Obsidian, but I'm a bit curious how the syncing works. I copied an Obsidian vault to a new folder, and when I start the import process in OpenKnowledge it asks me if I want it "shared" or "local only". If I select "Shared", where does the git repo live that other instances of OK sync from? edit: This seems to be "team-oriented" rather than geared towa…
Re: Show HN: OpenKnowledge – open source AI-first alternative to Obsidian/Notion
#59I've been using my opencode go subscription for Obsidian, saving my Claude sub for actual coding. Any reason why it's limited to Codex, Claude, and Cursor?
Re: Show HN: OpenKnowledge – open source AI-first alternative to Obsidian/Notion
#60Nice approach. Personally I’ve been trying very hard to migrate away from git+Obsidian project setup according to the OpenAI Harness Engineering. It works wonderfully in Codex Desktop. The only gotcha - I want to share knowledge bases with the team in a way that is: (1) versioned (a la git, not Notion) (2) usable from any chat (a la MCP) (3) basic access controls for team setup. (4) works through the interface that o…
Gotcha. We're optimizing for the same scenarios, may be worth a look at our implementation in case transferable to yours. See: #1 - the "autosync" and GitHub integrations do exactly this. #2 - The app auto-instals skills/MCP server configs for a few harnesses #4 - We embedded agentic-search capabilities via the MCP server (e.g. we virtualize 'ls' and 'cat' so we can enrich it for the agent for better hierchical navig…
So changesets have to be atomic across multiple documents and semantic (so that agents can resolve the changes). Weak per-document versioning isn’t enough here.
#4. Nice! Same story, but also virtualizing ripgrep, find and tree (plus MD-aware outline mode). With that setup even agents with weaker local models (eg runnable on DGX Spark) can solve complex tasks in the Agentic Commerce domain.