v0.63.0-beta.16

Delta since previous beta (v0.63.0-beta.15) — 1 new changeset.

Minor Changes

• One file on disk can no longer be backed by two separate collaboration documents. Addressing a document by a name that kept its .md or .mdx extension used to open a second, independent room over the same file. Both rooms then wrote to that file with no merge and no conflict shown, so whichever saved last silently overwrote the other, and an affected editor tab restored the broken state on every launch. Extension-qualified names now collapse onto the document they actually name, at the one point a room is keyed, so every surface converges: wiki links, graph nodes, share links, skill references, the preview URL, and the HTTP document routes. When a .md and an .mdx file genuinely exist side by side under one name, the document API still reaches each of them: the extension-qualified name serves the file the bare name does not. The editor lists such a pair as a single entry, so only one half opens there, and that is unchanged. Tabs carrying the old shape are repaired when they are read, so an affected install fixes itself on upgrade.

  • ok open now prints the project it resolved. Before, a path that landed in a different project than you expected looked identical to one that landed where you meant, and the only way to tell was to run ok ps afterwards. When the resolved project sits inside another OpenKnowledge project, the output names both.
  • --project is honored wherever you put it. Previously it worked only when it came before the target and the target had no file extension. In every other shape it was silently dropped and the project was derived from the file instead. When an override cannot be honored the command now fails and says why, rather than quietly opening somewhere else.
  • ok stop declines to stop a server that something is still connected to, naming how many clients are attached, and --force overrides it. This counts every kind of client, including agents, because stopping a server an agent is writing through loses work the same way. A server that cannot be reached is stopped without the check. ok deinit and ok uninstall do not gain a second prompt: they add a line to the plan they already show, noting that restarting will not bring those windows back.
  • A window whose server has stopped now offers to restart it from the file sidebar, which is the surface that reports the failure. The action already existed but only appeared in a transient toast and in the document error state, so it was easy to miss and the window read as permanently broken.
  • ok stop records what it stopped, and servers record why they exited. Neither left a durable trace before, so an external stop, an idle shutdown, and a crash were indistinguishable afterwards and none of them reached a diagnostic bundle. Log records also name the project actually resolved instead of a placeholder, and ok stop reports its target rather than the directory you happened to be in.
  • A project nested inside another project is no longer indexed by its parent. The two used to share content and reconcile only through disk writes.
  • runStop, exported for programmatic use, is now async and refuses by default when clients are connected. Callers must await it, and pass force: true for the previous unconditional behavior.

Downloads

Platform	Architecture	Download
macOS	Apple Silicon	OpenKnowledge-arm64.dmg
Windows	x64	OpenKnowledge-Setup-x64.exe
Windows	arm64	OpenKnowledge-Setup-arm64.exe
Debian / Ubuntu	x64	OpenKnowledge-amd64.deb
Debian / Ubuntu	arm64	OpenKnowledge-arm64.deb
Fedora / RHEL	x64	OpenKnowledge-x86_64.rpm
Fedora / RHEL	arm64	OpenKnowledge-aarch64.rpm