OpenWiki

CLI for creating and maintaining agent-readable documentation for a codebase. Treat it as a candidate docs-maintenance tool near Agent-Docs Mesh, not a replacement for Kevin's existing wiki/skills doctors.

Source Snapshot

The current MIT source is langchain-ai/openwiki at c5d41cbe91fd6105bfbd4a05ec7606708ae22e23, with 14,894 stars, 142 detected tests, three workflows, and two skill files at the 2026-08-12 capture. This materially strengthens maintenance evidence while leaving the local decision unchanged: generated documentation must preserve curated context, provenance, staleness, reviewable diffs, and rollback. Source: commit-pinned repository receipt, 2026-08-12

The reviewed local image shows a GitHub Actions-style workflow with npm install --global openwiki, openwiki --update --print, and a scheduled docs-update PR. The durable point is the workflow shape: the docs updater should run from source, produce a diff, and let humans or agents review the PR before it becomes canon. Source: local artifact review, 2026-07-06

Local Route

Use OpenWiki as a reference or candidate when a repo needs generated agent docs from code. Kevin's default remains Agent-Docs Mesh: root AGENTS.md, nearest local docs, skill registry, doctors, and wiki pages. OpenWiki becomes useful only if it improves one of those steps:

  • source-derived docs can be regenerated without overwriting curated human context;
  • updates land as reviewable PRs or diffs;
  • generated pages preserve provenance and staleness markers;
  • the agent can query the docs without hiding uncertainty.

Timeline