Factory adds AutoWiki: /wiki generates repo docs on every push
Two days after Factory 2.0 launched, Factory added AutoWiki, which turns a repo into structured engineering docs that update on every push and can be generated from Droid with /wiki. The feature keeps architecture and request-path context aligned with the live codebase.
TL;DR
- FactoryAI's product description says AutoWiki turns a repo into structured engineering docs that update on every push.
- FactoryAI's usage post says teams can generate a wiki from Droid with the
/wikicommand. - According to FactoryAI's feature summary, the generated docs cover architecture, key flows, systems, and request paths through the codebase.
- FactoryAI's examples post says Factory generated sample wikis for 100 open-source repos, including React, Kubernetes, Rust, and Grafana.
- FactoryAI's Software Factory framing positions AutoWiki as part of a larger "Software Factory" system that runs continuously with humans as the governance layer.
Factory also published a longer write-up on the broader Software Factory idea, and the launch post shipped with a product video that shows the wiki flow in action. The most concrete detail is still the command surface: /wiki runs inside Droid, while the feature description frames the output as living documentation tied to each push.
AutoWiki
The core pitch is straightforward: AutoWiki converts a changing repository into browsable internal docs, then keeps them synced as the code changes. FactoryAI's thread says the generated pages cover four specific layers:
- Architecture
- Key flows
- Systems
- Request paths
That scope is narrower, and more useful, than a generic code summary. Factory is targeting the parts of a codebase that usually rot fastest in hand-written wikis.
/wiki command
Factory put the feature directly into Droid rather than hiding it in a settings page. FactoryAI's example post says running /wiki in any Droid session generates a wiki for the current repo.
The launch post also points to sample output across 100 open-source repositories. The named examples, per FactoryAI's repo list, are React, Kubernetes, Rust, and Grafana.
Software Factory
Two days after Factory 2.0, the company framed AutoWiki as one component of a bigger automation loop. FactoryAI's post describes that loop as a "24/7 system" that continuously produces software while humans stay in the governance layer.
That framing matters because it places documentation generation alongside the rest of Factory's agent workflow, not as a standalone docs tool. The linked official write-up is where Factory pushes that broader system story.