Most tools that offer to organize your knowledge start by asking you to move it. OpenKnowledge starts by asking for a folder path. You open a directory that already contains markdown or mdx files, and that directory stays where it is, in whatever shape it already had.
That sounds like a small design choice until you look at what it rules out. No import wizard. No proprietary block format. No database that quietly becomes the real source of truth while the exported files rot. The README names the targets it expects you to point at: existing codebases, wikis, Obsidian vaults. Your repo's docs directory qualifies. So does the pile of meeting notes you have been dragging between text editors for years.
Editing markdown without feeling the markdown
The editing surface is billed as full true WYSIWYG, with the stated goal that working on a markdown file feels like working in a Google Doc or a Notion page. The README's own shorthand for the whole thing is Notion meets VS Code, which is a fair summary of the tension it is trying to resolve. Plain text files win on portability and lose on the writing experience, and most teams have quietly accepted that trade for a decade.
Around the editor sit the things you would expect from an IDE rather than a notes app: file navigator, search, tabs, and a graph viewer for wiki links. There is also support for embeddable HTML and rich components, aimed at engineering specs and visualized reports, which is the category of document where raw markdown usually gives up and people move to a hosted doc tool.
The install step that carries the weight
The interesting command is not the one that opens the editor. It is ok init.
npm install -g @inkeep/open-knowledge
cd your-project
ok init
ok start
ok init scaffolds the project and wires up the AI editors it detects on your machine. The README lists Claude Code, Claude Desktop, Cursor, Codex, OpenCode, and OpenClaw. What it installs is MCP and skills, described as designed to give agents enriched search and authoring of documents rather than whatever they would manage on their own against a directory tree.
Read that alongside the folder-first decision and the architecture gets clear. The editor is the human view of the files. MCP is the agent view of the same files. Neither one owns the data, and there is no sync problem between them because there is nothing to sync. Side-by-side AI editing is listed for Claude, Codex, OpenCode, and Pi, with any other harness reachable through MCP or the CLI.
This is the part worth stealing even if you never install the app. Teams keep building agent context layers that duplicate content into a vector store, then spend the next quarter reconciling drift. Pointing the agent at the same bytes the human edits removes an entire class of failure.
Sharing without a sharing service
Team sharing and auto-sync are described as no-code, powered by git and GitHub underneath, and they are optional. You can run the whole thing without touching them.
That framing matters for the privacy claim. The project describes itself as private, local, and free, and the sync story is consistent with that rather than working against it. Collaboration is a repo you already know how to audit, revert, and back up, not a hosted workspace with its own permission model to learn.
Practical notes before you try it
The desktop app covers macOS on Apple Silicon, Windows 10 and up on x64 or Arm64 with a per-user installer and no admin prompt, and Linux via deb or rpm. Intel Macs and servers go through the web app path instead, which runs the same editor locally and needs Node.js 24 or newer plus git.
The license is GPL-3.0 or later, which is fine for using the app and worth a closer look if you were planning to build on the code. The repo lives at inkeep/open-knowledge, and the project takes public pull requests and issues.
If you have been waiting for a reason to stop pasting documentation into a chat window, the wiring is the reason. The files are already there.
GitHub: https://github.com/inkeep/open-knowledge
Curated by Agent Palisade — practical AI for small and mid-sized businesses.
Top comments (0)