v0.20.0-beta.4
Pre-releaseDelta since previous beta (v0.20.0-beta.3) — 2 new changesets.
Patch Changes
-
Clarify the skills import prompt. The one-time banner now states what Import actually does: it moves the editor-dir skills into
.ok/skillsand replaces the.claude,.codex, etc. copies with symlinks back to it, so the knowledge base is the single place to edit them and every editor stays in sync. It also flags the consequences a user needs before clicking: if those folders are committed to git the change should be reviewed, and symlinks can behave differently on some editors and on Windows. -
Stop two ways agents get derailed around the skill surface.
-
The
skillsMCP tool now short-circuits OpenKnowledge's own built-in skills instead of 404-ing. An agent told to "load the open-knowledge skill" would callskills({ name: "open-knowledge" }), hit a bareSkill not found., and fall back to cat-ing the bundled SKILL.md. The built-ins (open-knowledge,open-knowledge-discovery,open-knowledge-write-skill) are runtime agent skills projected into editor host dirs, never KB content skills, so a READ aimed at one now returns a teaching error explaining it is already in the agent's loaded skill list and is not fetched through this tool. User-authoredopen-knowledge-pack-*skills are unaffected, and the tool description states the boundary up front. -
The project SKILL.md escape hatch now tells agents that their initial tool list is not exhaustive: some clients (notably Codex) defer MCP tools behind a lazy
tool_searchstep, somcp__open-knowledge__*is absent until discovered. Absence from the visible list means "not discovered yet," not "not registered" — agents must run tool discovery before invoking the native-tools escape hatch.
-