Download
Run knomit on your machine.
A tray app that runs the server for you, or the bare server binary. Local-first: your knowledge base is a git repo on your own disk.
v0.5.3 released 18 August 2026 Release notes
macOS
Apple SiliconSigned with a Developer ID and notarized by Apple. Drag it to Applications and open it — no right-click-Open, no trip through Privacy & Security.
Linux
x86_64A single AppImage. Needs GTK 4 and WebKitGTK 6.0 on the host.
Prefer to build it yourself? The quick start covers cloning and building from source, and everything here is open on GitHub.
Installing
Desktop
The desktop app boots a full knomit server inside itself on a loopback port and
shows the web UI in a native window. It also publishes a lockfile that
knomit-bridge discovers, so MCP clients find the running server without
being told a port. See the desktop guide.
On Linux, make the AppImage executable and run it. On a host without FUSE, prefix it
with APPIMAGE_EXTRACT_AND_RUN=1.
chmod +x Knomit-0.5.3-linux-amd64.AppImage
./Knomit-0.5.3-linux-amd64.AppImage Server
Extract and run. The native libraries resolve from the bundled lib/
automatically. The embedding model — around 600 MB — downloads on first run.
Every subcommand and flag is in the CLI
reference.
tar xzf knomit-0.5.3-<platform>.tar.gz
cd knomit-0.5.3-<platform>
./knomit serve
The server tarballs carry the same Developer ID signature as the app, but a tarball
cannot hold a notarization ticket — notarytool accepts only .zip, .pkg
and .dmg. Gatekeeper resolves those against Apple online, which needs nothing from
you on a connected machine.
Updates
macOS builds keep themselves current. They poll a signed feed every six hours and post a notification when a new version exists. knomit never opens a window to tell you, and a check that finds nothing is silent. Installing happens only when you press Install & Restart — an update may migrate your knowledge base, and migrations do not reverse. You can also check on demand from the tray menu.
Linux does not self-update yet. Download a newer AppImage to upgrade. The updater's binary-swap step resolves paths inside the AppImage's temporary mount rather than the AppImage file itself, so it stays disabled there until that is fixed upstream.
Verifying a download
Every artifact ships a detached .ed25519 signature over its SHA-256
digest, alongside it on the
release page. The macOS
updater checks that signature against a key pinned at build time and refuses anything
that does not match. To check by hand, compare the digest against the signed one:
shasum -a 256 <artifact>