OpenKnowledge Files

0.20.0

Stable promotion of beta v0.20.0-beta.14.

Aggregated changes since previous stable:

0.20.0-beta.0

Patch Changes

• Rename the ok install-skill CLI command to a deliberately hidden, unadvertised ok cowork. The old name implied an automatic install it never performed — it builds the openknowledge.skill bundle and opens the Claude Desktop App for a manual upload (the only path to the separate Skills list Claude Chat & Cowork read, which ok init's editor wiring can't reach). The command is now registered hidden (absent from ok --help), and ok init no longer pushes a hint toward it — it is a power-user escape hatch discovered pull-only via the Open Knowledge skill. The underlying bundle build and the POST /api/install-skill route are unchanged.

0.20.0-beta.1

Patch Changes

• Fix Open Knowledge Desktop offering to set up a project inside a subfolder of a linked git worktree. Picking a subdirectory (for example public/open-knowledge) inside a git worktree add checkout misclassified it as a worktree root and showed "Setup Open Knowledge in this folder" in place, scaffolding .ok/ in the subfolder instead of promoting to the git root. Subfolders of a linked worktree now correctly fall through to git-root promotion; only the worktree root itself is treated as a standalone project.

0.20.0-beta.2

Patch Changes

• Fix a bug where the same file could open in two tabs at once. Clicking a sidebar file that is already open in another tab now focuses that existing tab instead of opening a duplicate — including when a blank "New Tab" placeholder is the active tab (the active placeholder is consumed). The same focus-in-place behavior applies to folder and asset tabs. Tabs restored from a saved session that already contain two views of one file are left untouched.
• @inkeep/open-knowledge-core@0.19.3-beta.0
• @inkeep/open-knowledge-server@0.19.3-beta.0

0.20.0-beta.3

Patch Changes

• Docked terminal: an Open in terminal launch no longer prints a raw command not found. The launch gate now writes the <bin> '<prompt>' command only when a PATH probe confirms the CLI is present. On a flaky unknown probe it re-probes once; a not-found verdict, a still-unknown re-probe, or an IPC-level probe failure all suppress the write and surface the existing missing-CLI banner instead. This applies to Codex / Cursor / OpenCode (via cliPreflight) and to Claude (gated on the fresh claudePreflight recheck it already runs). The trade-off is a rare false-negative — an installed CLI whose probe flakes twice won't auto-launch — in exchange for a guaranteed-clean terminal.
• @inkeep/open-knowledge-core@0.19.3-beta.0
• @inkeep/open-knowledge-server@0.19.3-beta.0

0.20.0-beta.4

Patch Changes

• Clarify the skills import prompt. The one-time banner now states what Import actually does: it moves the editor-dir skills into .ok/skills and replaces the .claude, .codex, etc. copies with symlinks back to it, so the knowledge base is the single place to edit them and every editor stays in sync. It also flags the consequences a user needs before clicking: if those folders are committed to git the change should be reviewed, and symlinks can behave differently on some editors and on Windows.

• Stop two ways agents get derailed around the skill surface.

• The skills MCP tool now short-circuits OpenKnowledge's own built-in skills instead of 404-ing. An agent told to "load the open-knowledge skill" would call skills({ name: "open-knowledge" }), hit a bare Skill not found., and fall back to cat-ing the bundled SKILL.md. The built-ins (open-knowledge, open-knowledge-discovery, open-knowledge-write-skill) are runtime agent skills projected into editor host dirs, never KB content skills, so a READ aimed at one now returns a teaching error explaining it is already in the agent's loaded skill list and is not fetched through this tool. User-authored open-knowledge-pack-* skills are unaffected, and the tool description states the boundary up front.

• The project SKILL.md escape hatch now tells agents that their initial tool list is not exhaustive: some clients (notably Codex) defer MCP tools behind a lazy tool_search step, so mcp__open-knowledge__* is absent until discovered. Absence from the visible list means "not discovered yet," not "not registered" — agents must run tool discovery before invoking the native-tools escape hatch.

0.20.0-beta.5

Minor Changes

• Write-time broken-link validation in the Open Knowledge MCP. write/edit now return brokenLinks in the same response — outbound links that don't resolve are surfaced at write time, report-only so the write still lands and you can author a doc before its link target exists. Validation covers every local link, not just docs: the ./-onto-a-content-root-path doubling footgun and missing [[wiki]] / markdown doc targets (no-such-doc), root-escaping paths from one ../ too many (unresolvable), and links to assets or source files ([src](../../foo.py)) that don't exist on disk at the resolved path (no-such-file). That last reason closes the gap a real codebase-wiki run hit: wrong-depth source-file links that 404 silently because the doc-only link graph never tracked them. The platform and pack skills are updated to point agents at brokenLinks as the primary write-time check and to clarify that a same-pass forward-reference reports as no-such-doc until its target lands (the links({ kind: "dead" }) audit is the authoritative end-state check).

0.20.0-beta.6

Patch Changes

• Shorten the "Codebase wiki" starter-pack description to a single short clause ("Architecture, modules, and flows.") so its card matches the length of the other packs on the starter-pack picker instead of overflowing with a full paragraph.

0.20.0-beta.7

Patch Changes

• Desktop: add an opt-in path to fetch updates through the openknowledge.ai proxy so updates can be counted per version. When the build's channel is enabled, electron-updater's feed is pointed at openknowledge.ai/updates/{channel} and requests are tagged with x-ok-from-version / x-ok-channel headers. Default-off — production keeps reading the GitHub publish: config until the proxy is verified live, then the enabled-channel set flips to beta-first. A feed failure on the first check reverts to the GitHub provider for the session, so auto-update reliability never drops below GitHub-direct.

0.20.0-beta.8

Patch Changes

• Keep an open browser tab's ok start server alive. The web editor now holds a single, app-lifetime /collab/keepalive WebSocket — the same presence-invisible keepalive the desktop app and MCP shim already use — so the server's 30-minute idle-shutdown can no longer fire out from under an open tab when no document is focused or during a brief reconnect. Previously, with no doc open the only liveness signal was the per-document collab connections, so an idle tab could lose its server and every editor/tool call would fail until reload. Closing the tab still lets the server idle-shut-down normally, and the keepalive reconnects across a server restart on a new port. Multiple tabs each hold their own keepalive. The keepalive adds no presence-bar entry.

0.20.0-beta.9

Patch Changes

• Stop starter-pack and other card descriptions from overflowing their cards. The "Codebase wiki" starter pack and the slash-command MirrorSource / Mirror block previews had descriptions long enough to wrap to many lines and stretch their cards; those are now concise. The description text on the starter-pack picker, the slash-command block preview, the Navigator project-launcher cards, and the share-receive dialog is now line-clamped, so any long description truncates cleanly instead of distorting the layout.

0.20.0-beta.10

Patch Changes

• Fix ok start hanging for about 10 seconds on Ctrl+C when a live client was connected. If a browser preview tab or an agent/MCP session held a WebSocket open, shutdown left that socket alive, so the WebSocket-server close and the HTTP-server close each blocked until a 5-second internal timeout fired — adding ~10s of delay and printing an alarming AggregateError on a routine quit. Shutdown now drains the live upgrade sockets up front (mirroring the existing drain in ok ui), so both close steps finish promptly and the server lock is released right away.

0.20.0-beta.11

Patch Changes

• Desktop: stop showing the sticky "Installed CLI shims." startup toast when an app upgrade only repoints the internal ~/.ok/bin symlinks. The startup PATH-reclaim toast now fires only for changes the user can see or act on — a shell rc-file edit, an opt-out, a legacy-symlink cleanup, or a failure. A no-op symlink repoint (the common case on every upgrade or bundle-path change) is now silent; the repoint still happens and still emits the structured path-install-symlink-success event for operators. Restores the spec's "silent if no meaningful user-facing change" contract.

0.20.0-beta.12

Patch Changes

• Make "Open in agent" (handoff to Claude, Codex, and Cursor) work on Windows and Linux, not just macOS. Install detection was already cross-platform, so on Windows/Linux a registered agent showed an enabled row that, when clicked, failed with a 500 error and a "Couldn't reach …" toast. Handoff dispatch now opens the agent's protocol URL through the OS's registered handler on every platform (/usr/bin/open on macOS, rundll32 on Windows, xdg-open on Linux), and Cursor's workspace launch already worked cross-platform. On Windows/Linux the server first confirms the agent's URL scheme is actually registered, so an uninstalled agent reports "not installed" instead of a misleading success.

0.20.0-beta.13

Patch Changes

• Desktop: enable the openknowledge.ai update proxy for the beta channel. Beta builds now fetch updates through openknowledge.ai/updates/beta, which 302s to the byte-identical GitHub asset (preserving the manifest sha512 and the macOS signature) so updates can be counted per version. Stable still reads the GitHub publish: config; it gets the same path once an end-to-end beta update is confirmed. A feed failure reverts to the GitHub provider for the session, so auto-update reliability never drops below GitHub-direct.

0.20.0-beta.14

Patch Changes

• Run the git preflight at the project-setup boundary so a broken or PATH-invisible git surfaces recoverable install/upgrade guidance instead of a raw error.

Creating a project, opening a folder, cloning from GitHub, and ok init now verify git is usable before invoking it, and run against the exact git the preflight validated (the resolved path for in-process git, or an enriched PATH for the spawned clone). When git is missing or unusable they report platform-specific install guidance; ok init exits 78 (EX_CONFIG) on a git-preflight failure, matching ok start.

These setup paths now require git 2.31 or newer — the same floor ok start and the desktop app already enforce at launch.