v0.14.1-beta.9

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

Patch Changes

• The Create-new-project dialog in OK Desktop is now name-first. You type the project name in a focused field at the top, then see a read-only Location with a Browse button to change where it lands and a live "Will be created at: …" caption showing the exact folder before you commit. Naming a project no longer means using the OS folder picker's New Folder button or hitting an "already has files" wall first. A name that collides with an existing non-empty folder, or one that can't be turned into a valid folder name, is flagged inline on the name field. The nested-project and parent-git-repo guards are unchanged.

v0.14.1-beta.8

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

Patch Changes

• Add an AI prompt composer to the empty-state screens. Describe what you want to build and hand it off to your coding agent (Claude, Codex, or Cursor) — it composes a project brief and opens the agent to scaffold your knowledge base to match, using the same handoff path as "Open with AI". One-click starter prompts are tailored to the surface (build-from-scratch ideas on a brand-new project; spec / architecture prompts when the project already has content). The agent picker lists your installed agents and remembers your last choice per machine; when none are installed, Create is disabled with a hint.

  The composer now leads both empty-state surfaces; the old "With AI" editor-launch cards and the "New file" card on the post-init screen are gone (a "or create a new file" link covers blank files). Starter-pack descriptions are shorter and friendlier, and the "Entity vault (GBrain-compatible)" pack is renamed "Personal CRM".

  When OK runs embedded inside a host agent (Cursor/Codex/Claude) — where launching an agent would loop back — the empty state shows the same starter prompts as copy-to-paste rows instead, so you can grab one and paste it straight into the chat without leaving the agent.

v0.14.1-beta.7

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

Patch Changes

• Make the image / video / audio upload affordance discoverable on the property
  panel and consolidate alignment to one surface. Three changes:

  • Collapse three alignment surfaces into one. Image / video / Embed /
    CommonMarkImage previously exposed alignment in the floating bubble menu,
    in the per-block chrome bar, AND in the PropPanel Align Select. The
    bubble menu (ImageAlignButtons) is the canonical surface; the chrome-bar
    trio and PropPanel Select are removed, and the align PropDef carries
    hidden: true so the prop still travels through the registry (MCP queries,
    descriptor docs, render path) without producing a redundant control. The
    rest of the cluster (PRD-7054 origin findings) follows:

  • The upload control rendered as an icon-only square next to the URL input,
    which read as decoration; users skipped it entirely and fell back to
    URL-paste as the only "working" path. Replaced with a full-width labeled
    "Upload from computer" button that pairs the icon with explicit text — the
    visible label doubles as the assistive-tech accessible name, so the screen-
    reader contract stays intact without aria-label.

  • The asset-autocomplete dropdown bound its width with the Tailwind v3
    implicit-var() shorthand w-[--radix-popover-trigger-width]. In Tailwind
    v4 that form emits literal width: --radix-popover-trigger-width — invalid
    CSS, silently ignored — so the suggestion list auto-sized to its longest
    asset path (~550px-wide) and overflowed the parent prop panel, swallowing
    the upload affordance in the visual chaos. Switched to v4's parenthesized
    form w-(--radix-popover-trigger-width); a DOM-level regression test pins
    the syntax so a future revert fails CI instead of users.

v0.14.1-beta.6

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

Patch Changes

• The file sidebar no longer flashes a red "Could not reach server" error during a desktop auto-update relaunch. While the app restarts to install an update, the server is intentionally torn down for a few seconds — the sidebar now shows a calm "Relaunching to install the update…" notice instead, and quietly re-attempts the listing so it self-heals the moment the server returns (for example, when a relaunch is aborted). A genuine outage with no relaunch underway still surfaces the honest error immediately.

v0.14.1-beta.5

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

Patch Changes

• The "Share this setup with your team?" choice in both onboarding dialogs (Open-folder and Create-new-project) now sits at the top level as two side-by-side cards — Shared vs Local only — instead of being buried under "Advanced settings." The copy is shorter and plain-language; the technical detail (which files, git mechanics) stays in the info tooltip next to the question. Both dialogs render the same selector via a new shared SharingModeField component.

v0.14.1-beta.4

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

Patch Changes

• Introduce the docked terminal in OK Desktop — an embedded shell beside the editor for running your tools without leaving the app. Toggle it with ⌘J or the new top-level Terminal menu. It ships polished for daily use:

  • Matches your theme — light, dark, or system, and re-skins live when you switch themes (no restart).
  • Available by default — opens on first use with no consent dialog; disable it per-project in Settings.
  • Top-level Terminal menu — New Terminal and Kill Terminal, between View and Window like a native editor.
  • Trash to kill — actually ends the shell session rather than just collapsing the panel; reopening starts a fresh shell, while collapse keeps the session running.
  • Cleaner agent hand-off — launching an agent into the terminal no longer appends the web-only "open the editor in web view" line.

  Opening or starting a new terminal now focuses the input so you can type right away, and killing a terminal after an agent hand-off opens a blank shell instead of replaying the previous prompt.

v0.14.1-beta.11

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

Patch Changes

• Fix the empty-state "copy prompt" rows not working when OK runs inside an embedded host iframe (e.g. Claude). The copy buttons called the async Clipboard API directly, which the host frame's Permissions-Policy refuses inside an iframe — the rejection was swallowed silently, so nothing copied and the row never showed "Copied". The copy now routes through the shared clipboard adapter, whose execCommand fallback succeeds under the click's user activation where the policy-gated async write is blocked.

v0.14.1-beta.10

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

Patch Changes

• Reword the open-folder onboarding dialog. The title is now "Setup Open Knowledge in this folder?" and the description reads "Open Knowledge stores its configuration and internal files inside a newly created .ok directory in your project root folder." The pointer to "Advanced settings" is dropped from the description; the Advanced settings section and the top-level Share-this-setup selector are unchanged.

v0.14.1-beta.3

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

Patch Changes

• The Open Knowledge MCP server no longer emits a handshake instructions block. That block was injected into every project the (globally-registered) server connected to — including non-Open-Knowledge projects — which steered agents toward OK tools they could not use there. Agent guidance for OK projects is delivered by the installed open-knowledge project skill, which is the single source of that contract.

v0.14.1-beta.2

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

Patch Changes

• Publish-to-GitHub: pick the owner with a radio list and default to an org

  The "Publish to GitHub" dialog now renders the eligible owners as a radio list (one card per owner) instead of a dropdown, so every choice is visible at a glance. When you belong to one or more organizations the wizard pre-selects the first org rather than your personal account, since a knowledge base is far more likely meant for the team, and accidentally publishing it under a personal login is annoying to undo. With no org available it falls back to your own account as before.