What is OpenWiki?
OpenWiki is a LangChain project that has a coding agent research a repository and write a linked Markdown wiki into an openwiki/ folder, then keeps it current. Each factual statement is stored as a Grounded Claim pointing at versioned source evidence such as a file and line range, so an update rewrites only the pages whose evidence changed, and a clean update makes no model calls at all.
It runs two ways: inside a coding agent you already use (Codex, Claude Code, OpenCode, Cursor, GitHub Copilot CLI, Kiro, IBM Bob, Antigravity, Oh My Pi or Pi), using that agent's model session, or as a standalone CLI on its own Deep Agents documentation agent with fourteen model providers. It maintains an AGENTS.md block, exposes local search and read tools over MCP, links wikis across repositories into workspaces, and writes Google's Open Knowledge Format v0.2.
The repository was created on 22 June 2026, is MIT-licensed and has about 17,600 GitHub stars. The npm package is at 0.7.2 (9 October 2026) and was downloaded about 66,000 times in the last week of October.
Is OpenWiki worth it?
OpenWiki solves the problem that sinks most generated documentation: it rots, and nobody knows which parts. By attaching each fact to versioned source evidence, it can tell on the next run that a claim about retry handling cites lines that have since moved, and send only that page back to the model. Unchanged repositories cost nothing to update, because the check runs before any model call. Pages are saved one at a time, so an interrupted run resumes rather than starting again.
The integration model is the practical win. Run inside Claude Code or Codex, it borrows the agent's authenticated session and tools, so there is no second API key or bill to manage; the agent does the research and writing while OpenWiki owns the queue, the claims bookkeeping and the final indexes. Its MCP search and read tools are local, read-only and make no model calls, and the managed instructions tell agents to look things up for concrete questions rather than loading the wiki at the start of every task. Scheduled GitHub Actions, GitLab and Bitbucket jobs open a docs pull request when the wiki changes.
The defaults deserve a look. Telemetry is on: a single event per init or update with the command, outcome and, at setup, provider and connector names, never code or prompts; OPENWIKI_TELEMETRY_DISABLED=1 or DO_NOT_TRACK=1 turns it off. The graph visualiser pulls its libraries from a public CDN, so it does not work offline. A .openwikiignore keeps paths from being read, but the README notes the agent can still infer an ignored area from tests or commit messages.
The limits are those of a four-month-old project moving quickly: version 0.7.2, about 208 open issues and pull requests, and claims grounding that so far covers only repository code, not the personal-wiki connectors (Notion, Gmail, Slack, X) or LangSmith traces. Compared with Repomix, which packs a repository into one prompt each time, OpenWiki costs a full generation up front and pays it back on every later question and every incremental update.
Where it earns its place
A platform team owning a control plane, data plane and infrastructure repository
Let agents answer cross-repository questions without loading all three codebases
Generate a wiki in each repository, group them with openwiki link into a workspace, and agents search across all three through local MCP tools. Run through Claude Code or Codex, it adds no model bill beyond the agent's own session.
An engineering manager at a 30-developer company with stale onboarding docs
Keep architecture documentation current without assigning someone to it
Add the scheduled GitHub Actions workflow with a fine-grained token so it opens a docs-only pull request whenever claims go stale; reviewers merge it like any other change. Clean weeks make no model calls.
A staff engineer joining a large unfamiliar repository
Get an accurate map of the codebase in an afternoon
Install the Claude Code integration and ask the agent to initialise OpenWiki from source and tests, then open openwiki visualize for a graph beside a Markdown reader. Expect the first generation to take a full agent session's worth of tokens.
Before you commit
- Setup
- npm install -g openwiki (Node 22.22.0+), openwiki integrations install claude (or codex, cursor and others), restart the agent and ask it to initialise the wiki. Standalone: openwiki --init walks through provider, key and model.
- Integrations
- Ten coding-agent hosts; fourteen providers for the standalone CLI including OpenAI (default gpt-5.6-terra), Anthropic, Bedrock, Vertex, Copilot and OpenAI-compatible endpoints such as Ollama; CI templates for GitHub, GitLab and Bitbucket; Notion, Gmail, Slack, X, web search and Hacker News connectors for a personal wiki.
- Data and privacy
- Wiki and claims are plain files in your repository; keys sit in ~/.openwiki/.env. Telemetry sends one anonymous event per init or update by default; OPENWIKI_TELEMETRY_DISABLED=1 opts out. Repository content goes to whichever model provider or host agent you use. MIT licence.
- Cost at scale
- Free software. The first generation of a large repository is the expensive step; native runs can document up to 8 pages in parallel, and later updates only pay for pages whose evidence changed. Through a coding-agent host the cost sits inside that subscription.
- Limits
- About 208 open issues and pull requests at 0.7.2; host-driven runs are sequential and cover code wikis only; streaming-only gateways can return a blank wiki unless streaming is forced; OpenRouter low balances can trigger 402 errors without an output cap.
What’s good
- Grounded Claims tie each fact to versioned source lines
- No-op updates skip model calls entirely
- Runs inside ten coding agents on their existing session
- Local, read-only MCP search across linked repositories
What’s not
- Telemetry on by default
- Visualiser needs a public CDN, so no offline viewing
- Claims grounding covers code only, not connectors
- Pre-1.0, with about 208 open issues and PRs
Best for
Teams whose coding agents keep rediscovering the same codebase and who want a wiki that updates itself in pull requests rather than drifting.
OpenWiki alternatives
OpenWiki: common questions
- Is OpenWiki worth it?
- OpenWiki is the first agent-written docs tool that knows which of its own sentences have gone stale, and that is what makes generated documentation worth keeping. We rate it 4.2 out of 5.
- How much does OpenWiki cost?
- Free and open source (MIT). You pay your model provider directly.
- What are the downsides of OpenWiki?
- Telemetry on by default; visualiser needs a public CDN, so no offline viewing; claims grounding covers code only, not connectors; pre-1.0, with about 208 open issues and PRs.
- Who is OpenWiki best for?
- Teams whose coding agents keep rediscovering the same codebase and who want a wiki that updates itself in pull requests rather than drifting.
- How much does OpenWiki cost for a team or in production?
- Free software. The first generation of a large repository is the expensive step; native runs can document up to 8 pages in parallel, and later updates only pay for pages whose evidence changed. Through a coding-agent host the cost sits inside that subscription.
- Is OpenWiki safe for company data?
- Wiki and claims are plain files in your repository; keys sit in ~/.openwiki/.env. Telemetry sends one anonymous event per init or update by default; OPENWIKI_TELEMETRY_DISABLED=1 opts out. Repository content goes to whichever model provider or host agent you use. MIT licence.
- What are the best OpenWiki alternatives?
- The closest alternatives we have reviewed are Repomix, Graphify, code2prompt and claude-mem.
Answers checked Oct 31, 2026.
Make OpenWiki? Show this rating on your site
