AI Wiki introduction
Turn an indexed repository into navigable, source-cited documentation your team can trust.
The AI Wiki generates a navigable documentation site for a connected repository — an explanation of how the code is organized, what each part does, and why, with every page cited to the exact source files and line ranges it describes, pinned to the exact commit the wiki was generated from.
The same connected repos that power AI Review power the Wiki: one repository index, two ways to read it.
Wiki reader with navigation, a content page with citations, and the right rail visible.
Generate a wiki
From a connected repository, request a wiki generation. Generation is asynchronous — it reads and explains the whole repository, which takes time:
- Pending — the request is queued. If the repository has no usable index yet, the request waits in awaiting index until one is ready.
- Running — pages are being generated.
- Completed or Failed — when a generation completes, its pages publish atomically. If it fails, the previously published wiki stays live — a failed refresh never leaves you with nothing.
Regenerating always creates a fresh generation; a published wiki is never edited in place.
If your Workspace's plan doesn't include AI Wiki, the Wiki page offers a demo on a sample repository instead of generation for your own.
Reading a wiki
The reader is a three-pane layout — page navigation on the left, the page content in the middle, and an on-this-page rail with page actions on the right — built for trust. The full tour of the reader, citations, and demo mode is in Reading and citations.
- Navigation by structure — pages follow the repository's own organization, so "where does this live?" has the same answer in the wiki and in the code.
- Citations on every claim — pages reference the source files and line ranges their statements come from; a citation jumps straight to the source at the wiki's pinned commit.
- Diagrams — architectural pages render diagrams, with light and dark variants.
- Versions — past generations are retained, so you can read the documentation as it was at an earlier commit, and see how the codebase's story changed.
- Staleness you can see — when the repository has moved past the wiki's source commit, the wiki is marked stale with a visible since-time, so nobody mistakes old docs for current truth.
Keeping it fresh
Wikis can refresh automatically on a schedule your Workspace's plan allows, or be regenerated manually at any time. Admins can add custom instructions to steer tone and emphasis — for example, "focus on public APIs and configuration surface."
The full lifecycle — states, stale banners, failure behavior, and generation history — is in Refresh and generations.
When a wiki finishes generating, goes stale, or fails, Angada posts to Slack — so the team notices without watching a dashboard. Regenerating is possible directly from the Slack notification.