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
As of the 2026-07-06 check, npm has openwiki@0.0.1, MIT licensed, last modified 2026-07-01. The GitHub repo langchain-ai/openwiki has default-branch HEAD 23428de0cc0b1b6d3e5d09be413e92a5d6ee451f, tag 0.0.1 at ebc471289e449a482ec0ed4af0dcf5f516416244, MIT license, 7,144 stars, and 474 forks. Source: npm registry; GitHub API; git ls-remote, 2026-07-06
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
- 2026-07-06 | Page created from the July X bookmark batch. Local decision: keep OpenWiki as a candidate source-derived docs updater and route adoption through Agent-Docs Mesh rather than replacing Kevin's existing wiki/skill-doctor pipeline. Source: X bookmark artifact audit, 2026-07-06