v0.37.0

Minor Changes

• Add in-app AI agent threads via the Agent Client Protocol (ACP). "Open with AI" now includes a "Start an agent" option that runs a coding agent (Claude, Codex, Gemini, Cursor, Copilot, OpenCode, and the rest of the ACP registry) inside OpenKnowledge itself, in both the desktop app and the browser.

  "Start an agent" is available from every launch surface: the sparkles popover, the file-tree and empty-space right-click menus, and as a selectable default in the Ask AI and create-project composers. Every agent gets OpenKnowledge's MCP tools: agents that support HTTP MCP connect to the running server directly, and all others are handed a stdio bridge, so tools like search, write, and edit work regardless of the agent's transport support. When the agent's own harness already has OpenKnowledge's managed MCP entry installed (a project or user config written by ok init or the desktop consent flow), the thread skips injecting a second copy — the agent connects through the installed entry instead of two same-named servers fighting over which one loads. The check matches on what the entry launches (OpenKnowledge's own server command), so a harness's own per-tool approval settings layered onto that entry don't defeat it.

  Threads show the agent's messages, its plan, tool calls with diffs, and permission prompts, and you approve or decline each sensitive action. Agent replies render as markdown — headings, lists, tables, links, and code blocks with a copy button — live while the text streams, closing half-finished formatting cleanly mid-stream instead of flashing raw ** and backticks. Agents edit your notes through OpenKnowledge's own write path, so their changes are attributed to the agent and appear live in the editor. Each agent uses its own account and billing; nothing proprietary is bundled. Registry adapters install on first use and run as separate processes. For adapters that rely on an existing harness, OpenKnowledge detects locally installed Claude, Codex, Cursor, and OpenCode CLIs and offers those agents across the session dock, prompt composers, and Open with AI menus without overriding explicit choices or terminal defaults.

  Follow the file: while an agent works, the editor follows along, opening each document the agent creates, reads, or edits so you can watch the work happen live — including documents referenced through OpenKnowledge's own MCP tools (write, edit, move, and paths inside exec commands). Toggle it from the thread header (on by default).

  Switch agents any time: the thread dock's "+" lists every agent you've registered plus "Choose another agent…" to browse the catalog, so the first pick is never locked in. Reopening an empty sessions dock repeats that same preferred agent, CLI, or terminal choice, and the selected tab stays scrolled into view as the strip fills up. When an agent offers session settings — model, reasoning effort, fast mode, approval policy, or sandbox mode — they appear together in one labeled settings menu in the thread header (Agent Client Protocol session config options).

  Lifecycle and cost guarantees: closing a thread (or shutting down the server) kills the agent's entire process tree and waits for it to actually die, so a stuck agent can't keep running — and billing its account — invisibly after you close it. A turn still running with no window attached is asked to stop after 10 minutes and force-closed after 20. Stop shows "Stopping…" and, if the agent ignores the request, offers Force stop; a message that can't be delivered surfaces as a toast instead of vanishing; hiding the thread dock actually hides it. Long transcripts also render much more smoothly — events arrive in batches and the transcript updates incrementally instead of re-rendering the whole history on every streamed chunk.