v0.16.1

0.16.1

Stable promotion of beta v0.16.1-beta.12.

Aggregated changes since previous stable:

0.16.1-beta.0

(release body unavailable for v0.16.1-beta.0)

0.16.1-beta.1

Patch Changes

• Make /api/search report when its index is still warming, so cold-start searches retry instead of returning false-empty results.

  Right after the server boots, the workspace search index is still being built from the on-disk file walk. A search arriving in that window previously either blocked or came back empty as if nothing matched. The search endpoint now answers immediately with a ready: false signal while the index is warming, and ready: true once it is built.

  The search MCP tool surfaces this: instead of reporting "no matches" during warm-up, it tells the agent the index is still building and to wait a couple of seconds before retrying (or fall back to exec grep). The command palette shows its "Preparing search" status and polls until the index is ready, so results appear without retyping. This complements the earlier client-side cold-load fix by closing the same race at the server for every consumer.

0.16.1-beta.2

(release body unavailable for v0.16.1-beta.2)

0.16.1-beta.3

Patch Changes

• Make the first search after an edit faster on large workspaces.

  The workspace search index is rebuilt whenever the file index changes, and a rebuild previously re-read and re-parsed every markdown file on disk — so on a large workspace, the first search after any edit paid the cost of ingesting the entire corpus again. Each page's parsed search document is now reused across rebuilds when the watcher reports its file unchanged (by size, modified time, or inode), so a rebuild re-reads only the files that actually changed. Deleted and renamed pages drop out, and a failed read is retried rather than cached, so results stay current for typical edits.

0.16.1-beta.4

Patch Changes

• Fix the docked terminal resetting when you close a file or switch to a not-yet-loaded tab. Navigating to a doc whose provider was still loading transiently rendered a full-screen load skeleton outside the persistent editor column, which unmounted the terminal dock and killed the running shell. The skeleton now renders inside the persistent left column on mid-session navigation, so the terminal PTY and scrollback survive tab closes and switches (the cold-start load path is unchanged).

0.16.1-beta.5

Patch Changes

• Polish the create empty state and reorder the starter packs.

  The starter-prompt pills below the create composer now show only when starting a fresh project — on an existing repo the composer stays focused on a free-form brief, while the embedded copy-a-prompt list (shown when Open Knowledge runs inside a coding agent) keeps its suggestions in both cases. Tightened the spacing so the "Add a starter pack" and "create a new file" links sit just under the templates list instead of floating below it. In the starter-pack picker, the Worldbuilding and Open Knowledge Format packs swapped places.

0.16.1-beta.6

Patch Changes

• Remove the "Show all files" sidebar toggle; the file tree now always lists everything on disk except dotfiles.

  The sidebar previously had two visibility toggles — "Show hidden files" (dot-prefixed entries) and "Show all files" (files excluded by .gitignore / .okignore). "Show all files" is gone from every surface: the folder right-click menu, the sidebar empty-space menu, and the desktop View menu. The tree now always shows every file on disk — the previous "Show all files: on" default — so there is no way to scope it back to indexed/linked content. "Show hidden files" remains the single visibility toggle: off by default, revealing dot-prefixed entries when on. VCS and tooling internals (.git, .ok, node_modules) stay hidden in every mode, as before.

0.16.1-beta.7

Patch Changes

• Fix the appearance theme toggle flickering other open project windows. With more than one project open, switching Light/Dark/System made every non-focused window flicker rapidly before settling on the right appearance. The cause was the window-chrome translucency material being re-applied to every open window on every theme change — work that scales with the number of windows and rebuilds the macOS vibrancy view each time, even though the material never needs to change on a light/dark switch. The desktop app now skips re-applying a window's translucency when it is unchanged, so theme switches are flicker-free across all open windows. Genuine "Reduce transparency" accessibility changes still apply to every window.

0.16.1-beta.8

Patch Changes

• Update the markdown file icon in the file tree to a clearer document-with-"MD" glyph. The icon continues to follow the file tree's color treatment (muted gray by default, accented when its row is selected).

0.16.1-beta.9

Patch Changes

• Add a committed, project-level auto-sync default (autoSync.default). A maintainer can now ship a project that opens quietly for collaborators: set Settings → Sync → Default for everyone to "Off by default" (or "On by default") and the choice is committed to .ok/config.yml and travels with the repo via git. New clones then skip the "enable auto-sync" onboarding prompt and open with sync in the chosen state.

  autoSync.default is true | false | null (null/absent = ask, the previous behavior) and seeds each machine's autoSync.enabled on first open. It is a soft default — anyone can still change auto-sync for their own machine in Settings, which overrides the committed default for that machine only. The per-machine autoSync.enabled setting stays gitignored and per-machine.

0.16.1-beta.10

Patch Changes

• Add a property by pressing Enter in its value field.

  When adding a frontmatter property, typing a name, pressing Tab, typing a value, and pressing Enter now commits the new property — the whole interaction is keyboard-driven. Previously Enter in the value field only settled the value and blurred the input, so the property was not added until you clicked "Add" with the mouse. This works for text, number, and date values, in both the document property panel and a folder's properties; editing an existing property's value keeps its prior Enter-to-settle behavior.

0.16.1-beta.11

Patch Changes

• Refresh social links and resource navigation across the app and docs site:

  • The editor's Resources popover drops the standalone "Website" row and adds an "Open Knowledge" entry (brand logo, desaturated to sit with the monochrome icons and regaining color on hover) as the last item.
  • The docs site nav gains brand icons for GitHub and Discord, with X rendered icon-only (its label preserved as the accessible name).
  • Social links now point at the Open Knowledge handle (x.com/OpenKnowledgeAI) and the project Discord, replacing the legacy Inkeep X/LinkedIn destinations in the footer and structured-data sameAs.
  • The home hero and bottom call-to-action add a subtle "or CLI" link beside the macOS download button, pointing at the CLI reference.

0.16.1-beta.12

Patch Changes

• Fix starter-pack templates showing their frontmatter as raw text in the editor.

  Template files stored two stacked frontmatter blocks: the template's own title and description, then the frontmatter a new document receives. Editors only recognize the first block, so the second one leaked into the document body and showed up as raw --- fences and key: value lines instead of editable properties.

  Templates now use a single frontmatter block, with the template's identity under a reserved template: key and the new-document defaults as top-level keys. Creating a document from a template still produces the same frontmatter, with {{date}} and {{user}} substituted as before — including from an agent via write({ document: { template } }). Templates already on disk keep working and convert to the single-block shape the next time they are saved, so there is no migration step. This also fixes one starter template whose description contained an unquoted colon that broke YAML parsing, and adds a guard test so that class of bug cannot ship again.

  The template edit dialog is reworked to match: the title field is labeled Title, a dedicated Type field carries the Open Knowledge Format type, and a Default properties editor exposes the rest of the new-document frontmatter as editable key/value rows — so the starter content is now plain markdown instead of a raw frontmatter block. Every document created from any starter template carries a semantic type plus a one-line description summarizing what that kind of document holds, which you then specialize per document.