Desktop app
knomit-desktop is a native Wails v3 application: a
system-tray icon plus a native webview window showing the same web UI. It is the
easiest way to keep a knomit server running on your machine — no terminal, no
manual serve.
It works differently from a bare knomit serve, and those differences matter for
wiring up MCP clients.
How it differs from knomit serve
Section titled “How it differs from knomit serve”- Runs the server in-process. The app boots the full knomit server inside
itself on a looknomitck port (it prefers
19278, but picks a free port if that’s taken) and serves the web UI from embedded assets. That port is a pure REST/MCP endpoint — the same one Claude Code and other MCP clients call. - Publishes a discovery lockfile. On startup it writes
server.json({pid, port, version}, mode0600, written atomically) soknomit-bridgecan find the running server’s port without being told. The file lives outsideKNOMIT_HOME:- macOS:
~/Library/Application Support/knomit/server.json - Linux:
$XDG_STATE_HOME/knomit/server.json
- macOS:
- Lives in the system tray. On macOS it runs as a tray app
(
Knomit.app). On Linux it runs headless (no systray);knomit-desktop windowopens the webview, normally triggered from the installed.desktoplauncher. - Symlinks the bridge. The macOS app symlinks the bundled
knomit-bridgeinto~/binon launch, giving MCP clients a stable path to point at.
Build & install
Section titled “Build & install”Build the app with make desktop:
- macOS — produces
dist/darwin-arm64/Knomit.app. Launch withopen dist/darwin-arm64/Knomit.app. - Linux —
make desktop-installcopies the binary to$XDG_BIN(default~/.local/bin), an icon to the hicolor theme, and aknomit-desktop.desktoplauncher to$XDG_DATA/applications.
Logs go to stderr and a rotating file under the platform logs dir
(~/Library/Logs/knomit on macOS, $XDG_STATE_HOME/logs/knomit on Linux). See
the CLI reference for the
full argument list.