Factory AutoWiki
Factory AutoWiki turns a repository into generated, structured engineering docs that can be refreshed on every push and surfaced in the Factory app, GitHub Wiki, Droid sessions, and committed
droid-wiki/artifacts. It validates the doctrine that docs are a build artifact, while Kevin's local Agent-Docs Mesh keeps ownership over hand-written routing, fill slots, and doctors. Source: Factory AutoWiki docs, 2026-06-30
Routing Summary
Use Factory AutoWiki as a reference pattern when a repository needs generated source-derived documentation that refreshes with code changes. Route local implementation through Agent-Docs Mesh and wiki doctors first; use AutoWiki to inform generated-doc shape, source hashes, refresh cadence, and agent-readable repository maps.
Product Shape
AutoWiki is Factory's repository-documentation feature for Droid. The on-demand command is /wiki; the automated setup command is /install-wiki. Generated docs include architecture overviews, module breakdowns, key flows, systems, request paths, and cross-linked pages. Source: Factory docs, 2026-06-30
The important product idea is docs as build artifact. Factory describes wiki generation as source-derived, organized around the codebase, refreshed as the repo changes, and compared against previous commits for incremental updates. That makes documentation part of the repo's operating loop rather than a separate stale prose chore. Source: Factory article, 2026-06-17
Open-Source Gallery Proof
Factory's public Open Source AutoWikis page turns the product claim into a browsable corpus: 100 repositories, 4.7k generated pages, 14 languages covered, and 6.7M GitHub stars indexed. The gallery includes repos such as React, Kubernetes, Next.js, Grafana, Laravel, Node, Supabase, and Neon, so AutoWiki is being positioned as broad codebase-map infrastructure rather than a one-off Factory demo. Source: Factory Open Source AutoWikis, 2026-07-01
The gallery also clarifies the intended page taxonomy. Generated wikis include architecture, systems, packages, contribution guides, project lore, diagrams, video walkthroughs, and API maps. That taxonomy is useful for Kevin's local Agent-Docs Mesh because it separates generated structural maps from the hand-authored operating docs agents should obey. Source: Factory Open Source AutoWikis, 2026-07-01
Visual review: the attached bookmark image shows the AutoWiki gallery with metric tiles for repository count, generated pages, language coverage, and stars indexed, plus featured repo cards. The artifact is stronger than the original announcement screenshot because it proves browseable breadth, not just feature existence. Source: X/@FactoryAI visual artifact, 2026-06-18
Surfaces
AutoWiki exposes the same generated knowledge through multiple surfaces:
| Surface | Role |
|---|---|
| Factory App | Browse, search, and export generated wiki content. |
| GitHub Wiki | Sync generated pages into {repo}.wiki.git after the GitHub Wiki is initialized. |
| Droid sessions | Let Droid read wiki context through read_wiki rather than re-deriving codebase structure. |
droid-wiki/ |
Optional committed artifact path for repository-local documentation. |
Cloud Sync is enabled by default. Enterprise organizations can disable AutoWiki Cloud Sync; the docs say generation will not store wiki content, GitHub Wiki sync is skipped, and protected endpoints return 403. Source: Factory docs, 2026-06-30
Boundary With Kevin's Stack
Factory AutoWiki should influence Kevin's stack, not replace it. Agent-Docs Mesh already separates root reference (AGENTS.md), executable procedure (SKILL.md), append-only history (memory.md), and routing (RESOLVER.md). Generated docs are strongest for repository maps and architecture summaries; Kevin's mesh still owns policy, workflow semantics, fill-slot prose, doctor checks, and agent routing.
The local rule is therefore:
- Use AutoWiki as a reference pattern for generated docs, source hashes, and refresh-on-push behavior.
- Do not overwrite hand-authored
AGENTS.md,SKILL.md, or fill slots with generated prose. - Put generated docs behind a doctor that checks staleness, links, source hashes, and ownership boundaries.
Versioning
AutoWiki is a hosted Factory feature, not a public package. Version authority is docs and release dates:
| Source | Snapshot |
|---|---|
| Factory article | Published 2026-06-17, modified 2026-06-22. |
| Factory docs | Checked 2026-06-30; documents /wiki, /install-wiki, Cloud Sync, GitHub Wiki sync, and enterprise controls. |
| Open Source AutoWikis | Checked 2026-07-01; shows public gallery scale and generated page taxonomy. |
Record docs dates instead of pretending there is an npm or GitHub release to pin.
Timeline
- 2026-07-01 | Deep-reviewed the Open Source AutoWikis bookmark, inspected the local gallery image, and added the public corpus proof: 100 repos, 4.7k pages, 14 languages, 6.7M indexed stars, plus the generated page taxonomy. Source: X/@FactoryAI, 2026-06-18; https://factory.ai/open-source-wikis
- 2026-06-30 | Deep-reviewed Kevin's bookmark, inspected the local AutoWiki media artifact, read Factory article/docs, and promoted AutoWiki into a focused tool page plus Agent-Docs Mesh comparison. Source: X/@FactoryAI, 2026-06-17; Factory docs, 2026-06-30
- 2026-06-17 | Factory introduced AutoWiki as repo-derived engineering documentation for Droid and Factory. Source: Factory article, https://factory.ai/news/wiki