Skip to content

Releases: inkeep/open-knowledge

v0.35.1-beta.8

v0.35.1-beta.8 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 20 Jul 22:47

Delta since previous beta (v0.35.1-beta.7) — 1 new changeset.

Patch Changes

  • Version-history recording is dramatically cheaper on large knowledge bases and slow (mounted/network) volumes. The background history snapshot now reuses a persistent git index so unchanged files are no longer re-read and re-hashed on every save cycle (up to ~11x faster tree builds on a 10k-file KB); switching git branches with many open documents batches its bookkeeping into a few git calls instead of four per document (a 100-document switch drops from ~15s to well under a second); and agent writes coalesce into the normal debounced history commit instead of forcing a full commit per write, while history reads still always reflect every completed write.

v0.35.1-beta.7

v0.35.1-beta.7 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 20 Jul 20:58

Delta since previous beta (v0.35.1-beta.6) — 2 new changesets.

Patch Changes

  • Fixed a bug where deleting a template left the app unclickable until reload. The template row's actions menu opened a modal confirmation dialog while itself being a modal menu, stacking two pointer-events: none body locks; the post-delete refresh then unmounted the still-open dialog before Radix could unwind the lock, freezing every button (including "New" and "New template"). The menu is now non-modal, matching the file tree and project switcher.

  • OK Desktop can now open a single markdown file without setting up a project. The single-file editing session that ok <file> already provides is now reachable from the app itself: File → Open file… (⇧⌘O), the Cmd+K palette, and the Project Navigator, each opening a native .md/.mdx picker. Loose files also open via Finder's Open With → OpenKnowledge. These flows open the file in a temporary session and never write a .ok folder into its directory, so previewing one file no longer risks turning its parent folder into a project. A picked file that already lives inside a project opens that project instead.

v0.35.1-beta.6

v0.35.1-beta.6 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 20 Jul 20:42

Delta since previous beta (v0.35.1-beta.5) — 4 new changesets.

Patch Changes

  • Bug-report bundles now capture why the server died and what the MCP server was doing. A fatal server crash (uncaught exception or unhandled rejection) writes a synchronous last-server-crash.json record — timestamp, error name/message/stack, pid, uptime — under .ok/local/ plus a final fatal line in the server log, both collected into ok bug-report and ok diagnose bundle output; previously a hard crash lost the async log sink's tail and bundles could only say "server not running". The global MCP stdio server's [mcp] stderr diagnostics are now also mirrored to ~/.ok/logs/mcp.<date>.log (pruned at each startup by a 7-day age window and an aggregate size cap), so bundles include the agent-ingress diagnostics that previously landed only in the MCP host's own log folder.

  • The exec MCP tool's post-command mutation safety sweep is now scoped to the paths the command can actually touch (its own path operands), instead of statting up to 1000 files across the whole knowledge base twice on every call. Path-scoped commands like cat notes/a.md or grep -rn oauth articles/ now sweep only those paths, making exec noticeably cheaper on large knowledge bases. When the sweep does cover the whole tree (bare ls, find, recursive grep with no directory) and the corpus exceeds the 1000-file scan cap, the response now carries an explicit warning that mutation detection was partial, instead of silently presenting a capped sweep as full coverage.

  • The sidebar's page directory no longer storms the server during bulk agent writes. File-change pushes now coalesce into a single trailing refetch (~300 ms window) instead of refiring the full page-list and document-list walk on every push, so an agent writing many files per second no longer triggers ~10 full corpus refetches and index rebuilds per second. The initial load and manual refreshes stay immediate.

  • New operational metrics for cloud/server operators (all zero-overhead when telemetry is disabled): event-loop delay percentiles (ok.server.event_loop.delay_ms), CPU utilization (ok.server.cpu.utilization), extended memory sections (external, array_buffers) on ok.server.memory.usage_megabytes, a loaded-documents gauge (ok.server.docs.loaded), and write-spine queue depths (ok.persistence.queue.depth, ok.bridge.drain_backlog). Error responses now stamp their correlation UUID on the active trace span (ok.error.instance) so a client-reported error can be joined against its trace. The standard OTEL_TRACES_SAMPLER / OTEL_TRACES_SAMPLER_ARG sampling contract is now pinned by tests and documented, including its interaction with the local bug-bundle span sink.

v0.35.1-beta.5

v0.35.1-beta.5 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 20 Jul 20:29

Delta since previous beta (v0.35.1-beta.4) — 1 new changeset.

Patch Changes

  • Diagnostics bundles now capture more of what matters for content-loss triage. The full bundle stages the shadow repo's recovery-checkpoint refs (state/checkpoint-refs.txt — ref name, date, and content-free subject per checkpoint) and a new state/agent-effects.json snapshot of the per-document agent activity ring buffers, served by a new loopback-only GET /api/metrics/agent-effects endpoint that summarizes agent writes as character counts (never raw text). Doc names in the new artifacts are anonymized by the existing --redact pass, which now also hashes the agent-presence bundle's currentDoc path so a redacted state/agent-presence.json no longer leaks the document a person was editing. The web client's log forwarder also stops losing entries silently: drops from buffer overflow or failed uploads are counted and recorded as an explicit droppedSinceLastFlush gap marker in the server log on the next delivered batch, and a failed recovery-checkpoint write now also emits a structured server-log line with doc and branch context.

v0.35.1-beta.4

v0.35.1-beta.4 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 20 Jul 20:07

Delta since previous beta (v0.35.1-beta.3) — 1 new changeset.

Patch Changes

  • Add "Import as template" to the File Tree context menu. Right-click a markdown file to copy it into the folder's .ok/templates/, with the option to keep the original or convert it (delete the source). Backed by a new POST /api/template/import endpoint that carries over the source frontmatter.

v0.35.1-beta.3

v0.35.1-beta.3 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 20 Jul 19:51

Delta since previous beta (v0.35.1-beta.2) — 1 new changeset.

Patch Changes

  • Added OpenClaw and Hermes as "Open with AI" terminal launch targets in OK Desktop, alongside the existing agent CLIs. OpenClaw opens its interactive TUI seeded with the composed prompt via openclaw chat --message '<prompt>'. Hermes has no starting-prompt argument (its only prompt-carrying modes run once and exit), so OK launches hermes chat and, once Hermes signals its input is ready, delivers the prompt as a bracketed-paste write — bracketed paste keeps a multi-line prompt intact and inert to the TUI's key handling, then submits it. The paste waits for Hermes' readiness signal (with a timeout fallback) rather than a fixed delay, so it lands cleanly on slow and fast boots alike. Both were already supported as MCP servers; this adds the one-click terminal handoff.

v0.35.1-beta.2

v0.35.1-beta.2 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 20 Jul 17:40

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

Patch Changes

  • Auto-restart a leftover server after an app update, and drop the dev "started a fresh server" notice

    When OpenKnowledge Desktop auto-updated, a server for a project could survive the pre-install teardown (a CLI-spawned one, or one whose shutdown timed out). The relaunched app then attached to that stale build and asked you to click "Restart with this app's version" before it worked. Now, on the first launch after an update, the app detects the version-mismatched leftover and restarts it to match automatically — no prompt. This only happens on the launch right after an update: a running server that merely differs in version (for example a newer CLI you started yourself) is never auto-restarted. No extra notice appears — the existing "Updated to Version X" banner already tells you the app updated.

    The dev-only "Started a fresh OpenKnowledge server…" toast that popped up whenever a dev session reclaimed a leftover server is removed — the reclaim still happens, just silently.

v0.35.1-beta.1

v0.35.1-beta.1 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 20 Jul 17:10

Delta since previous beta (v0.35.1-beta.0) — 1 new changeset.

Patch Changes

  • /image now keeps the src field focused without immediately opening asset suggestions, so Upload from computer stays visible. Suggestions still open when you click or type in src, or use the arrow keys.

v0.35.1-beta.0

v0.35.1-beta.0 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 20 Jul 14:43

Delta since previous beta (v0.35.0-beta.12) — 1 new changeset.

Patch Changes

  • Timeline version and agent activity diffs now render as formatted WYSIWYG documents with changes marked inline. A Source toggle keeps the raw markdown diff as well.

v0.35.0-beta.12

v0.35.0-beta.12 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 20 Jul 09:50

Delta since previous beta (v0.35.0-beta.11) — 1 new changeset.

Patch Changes

  • The desktop app no longer invites you to file a bug report after your machine reboots (kernel panic, forced restart, or power loss) while OpenKnowledge was running. It now recognizes when the previous session ended because the machine went down — not because the app crashed — and skips the prompt in that case, logging the event instead. Genuine app crashes still prompt exactly as before, and a crash that produced a crash dump still prompts, even across a reboot.