v0.18.0

Minor Changes

• Add the codebase-wiki starter pack — an agent-authored, navigable wiki of your codebase. ok seed --pack codebase-wiki scaffolds a wiki/ knowledge base (architecture, modules, flows, concepts, and guides — each with a page template) plus an OVERVIEW hub and a generation log. The new workflow({ kind: "wiki" }) guide drives an agent to generate — and later incrementally refresh — the wiki from source, with mermaid diagrams, cross-linked pages, and source references, tuned by two natural-language knobs (audience: internal/public, depth: tour/standard/exhaustive). Version-controlled and private by default; the wiki doubles as durable grounding context for future agent sessions.

Patch Changes

• Add a persistent "Ask AI" prompt composer to the bottom of the OK Desktop editor. When a document is open, a small "Ask AI" pill sits above the editor footer; press Cmd+L (Ctrl+L on Windows/Linux) or click it to expand a freetext composer, type an instruction about the current doc, and send it to your coding agent (Claude, Codex, or Cursor) without leaving the editor. It reuses the same handoff path as "Open with AI" and "Edit with AI", scoping the prompt to the current document. The agent picker lists your installed agents and remembers your last choice per machine, and the empty composer shows rotating example prompts (a single static suggestion when reduced motion is requested). The composer stays out of the way when it does not apply: it is hidden while the terminal is open, in embedded or web hosts, and when no document is open.

  You can also pull a highlighted passage into the prompt as context: select text in the document and a removable snapshot pill appears in the composer. A short single-line selection is inlined verbatim; anything longer is sent as a reference the agent reads back from the file (line numbers in source mode, a passage anchor in rich-text mode), so the prompt stays compact. The pill persists when you move the cursor or click into the composer, is replaced when you highlight something new, and clears with its × or after you send.

  The project-wide "Create Something Great" composer on the empty-state screen now supports the same @-mentions: type @ to reference existing docs and files as chips, so a create brief can point the agent at the parts of the project to build on. The referenced paths are passed through to the agent alongside your brief.

• Fix internal document links opening in the wrong place from the desktop app. "Open in new tab" (Cmd/Ctrl-click, or the link panel's open-in-new-tab) on an in-app document link now navigates to that document inside Open Knowledge. Previously the desktop window handler treated the in-app route as an external URL: in development builds this opened a localhost tab in your web browser (and repeated follows could flood the browser with tabs), and in packaged builds the click did nothing.

• Keep illustrative example links in the starter packs out of the link graph, and clear the fullscreen graph title from the macOS traffic-light buttons.

  Several starter-pack examples used forms that the link indexer still extracts, so docs seeded or instantiated from them carried links to placeholder targets (path/to/doc-a, companies/acme, another-concept, …) that surfaced as phantom dead-links and red "missing" nodes in the graph:

  • The entity-vault log.md wrapped its "Example entry shape" block in an HTML comment. Comments don't render, but the indexer reads links inside them — it is now a fenced markdown code block (which the indexer skips), matching the knowledge-base pack. The example also renders as a visible, copyable template.
  • The entity-vault person/company/meeting templates and the OKF concept template had bare example links in their instructional prose, which every instantiated dossier/concept then inherited. They are now inline code, matching how the folder descriptions already write the same examples.

  To exclude an example link from the broken-link detector in your own docs, put it in a code fence (block) or inline code (inline) — an HTML comment will not.

  In the expanded (fullscreen) graph, the "GRAPH" title sat flush against the macOS traffic-light buttons: the header's safe-area reserve clears the button footprint, but the flush-left title was left touching the buttons. The left title cluster now gets a small margin in fullscreen so it clears them; the header keeps the shared safe-area reserve token unchanged.