Auto-generated codebase wiki: docs that stay current

Graphify now writes a codebase wiki for every repository you index, and rebuilds it alongside each index so it describes the latest build. The feature has been live since October 8, and the company described it in a blog post on October 14.

What the wiki contains

Graphify reads the code graph for a repository and produces articles on what each area does, its key components, and the decisions and caveats behind them. You open Wiki in the console, pick a repository, and read it like an internal docs site, with an outline for long pages.

Why it stays current

The wiki is built with each index of the default branch, so it moves when the code moves. Graphify's argument is that hand-written docs drift because nobody's job is to update them on every merge, and a generated wiki removes that update step. It does not replace READMEs: design intent and how-to guides still belong in your own docs.

Checking its claims

Each article links the source files it was written from. A "How we know" panel shows where its claims came from. For anything that matters, such as before changing the code it describes, the advice is to open the file and confirm it.

Wiki or Ask

The wiki suits orientation: what lives where, and how a subsystem fits together. For a question that spans the code, such as which paths reach a function, use "Ask the wiki instead" from search, or open Ask, to get an answer grounded in the graph with citations. Search finds words inside articles, while Ask follows the graph.

Because the wiki and agents read the same graph, what a person reads in the wiki and what an agent retrieves over MCP agree. Graphify points to onboarding a teammate, reviewing a service you do not own, and preparing a design discussion as typical uses.

Getting started

Index a repository in Graphify and open Wiki once the build finishes. Nothing needs to be written by hand. For local work, the open-source Graphify CLI installs with uv tool install graphifyy.