AutoWiki (Factory.ai)
Factory.ai’s multi-agent system that auto-generates and continuously maintains a wiki from a codebase — its slogan: “Documentation should be a build artifact, not a side project.” The clearest commercial instance yet of the machine-maintained wiki idea this hub is built on (cf. research-wiki’s llm-wiki lineage), packaged as an agentic coding product rather than a tools-for-thought app.
How it works
A multi-phase, multi-agent pipeline: Survey (structural + semantic repo analysis) → Plan (wiki
structure) → Generate (pages in dependency order) → optional narrated video walkthroughs → Upload.
Runs are incremental — only pages affected by a code change regenerate, so the docs stay current via
automated refresh on every push (GitHub Actions / GitLab CI). Output lives in-repo under droid-wiki/,
with a web viewer (full-text search + version history) and GitHub-wiki sync.
Why it matters here
Two threads of this spoke converge in it:
- Documentation as a build artifact — the same “agents need structure, not just raw model power” thesis behind agentic-coding-harness: a generated, dependency-ordered, auto-refreshed knowledge base is infrastructure, not prose.
- Shared context for humans and agents — Factory’s Droids browse and search the wiki natively in-session, so AutoWiki doubles as agent context: the codebase’s knowledge becomes retrievable grounding for the agents working on it (the loop where agents both produce and consume the docs).
Cross-spoke
The dominant substance is an agentic coding tool, so it ingests here; but it’s also a concrete instance of research-wiki’s llm-wiki concept (a machine generating/maintaining a file-based markdown wiki) — the runner-up home. Linked, not duplicated.
Tier
T2 — first-party vendor announcement (primary on what the product is, but promotional; the multi-agent pipeline and auto-refresh claims are Factory’s own, not independently benchmarked).
OSS counterpart
openwiki (LangChain) is the open-source CLI version of the same idea — survey a repo, generate docs, auto-refresh on push via CI — and wires the output into agents by appending to AGENTS.md/CLAUDE.md rather than a hosted web viewer. Two independent teams, one shape.
Related
openwiki · agentic-coding-harness · agent-memory · building-effective-agents · loop-engineering · llm-wiki · synthesis