Skip to main content
Wiki turns an indexed repository into a browsable knowledge base: its subsystems, its load-bearing abstractions, and how they connect. Pages are generated from the code knowledge graph, and each one keeps a confidence trail, so you know which statements were read from the code and which were inferred.
Use the wiki when you’re onboarding to a repository, explaining it to someone new, or looking for the right place to start reading code.

Before you start

  • A Graphify account at app.graphify.com.
  • An indexed repository. The wiki is generated from a build, so a new repository shows No wiki for this build yet until its build finishes.
  • Wiki in your workspace navigation. If you don’t see it, it isn’t turned on for your workspace.

Read the wiki

1

Open it

Open Wiki in the Console and choose a Repository.
2

Pick an article

The sidebar starts with Overview, then Subsystems, the main parts of the code, with each one’s areas underneath. Areas that aren’t part of a subsystem come next, production code first, then tests, vendored code, tooling, and docs. The Glossary comes last. Use Search pages to jump to a topic. Search covers subsystem pages and the glossary too.
3

Read

Each article has Key components, diagrams you can expand, and Relevant source files. On this page lists its sections, and Previous page and Next page move through the wiki in order.
4

Go to the code

Open the source opens the file. Show in the graph opens the component in Graph explorer.
Turn on Reading mode to hide the surrounding Console while you read.

Diagrams

The Overview page has an architecture diagram of the repository. Click a box to open its page. If a diagram is bigger than its frame, drag it to see the rest, or expand it. The zoom and expand buttons sit under the diagram. On a phone, swipe sideways to pan and up or down to scroll the page. A wiki built before subsystems were added keeps its older sidebar, grouped by folder.

Confidence labels

Ask the wiki

Select Ask the wiki (or Ask about this project) and type what you’d like to understand. Answers draw on the same graph as the wiki. For questions about one function or call path, Ask is more direct.

Large repositories

For a very large graph, the wiki covers only its largest areas, and some cross-links may not resolve. If a wiki is too large to load, contact support to raise its size limit.

Keyboard shortcuts

Each page lists its Relevant source files and Key components. Use Open the source to see the code, or Show in graph to find it in Graph explorer. When the wiki is Behind the latest commit, it shows Updating to the latest commit while a new build runs.

Starter questions

Ask about this project opens a panel with starter questions. You don’t need code terms:
  • “What does this project do? Explain it in plain language.”
  • “What are the main parts of this project, and how do they work together?”
  • “Where does a request or user action start in this project?”
Answers use the indexed code and say when evidence is missing.

Wikis for Google Drive folders

A synced Google Drive folder gets a wiki too, built from its documents. Its states read Sync in progress, Folder not synced and Folder sync failed, instead of the repository states. Google Drive syncing requires a paid plan.

Verify and troubleshoot

It reflects the latest build of the repository. Check the build metadata on the page.
Yes. Open-source Graphify can export a Markdown wiki with graphify export wiki. See Exports.
Verified means read directly from the code. Inferred means worked out by analysis. Needs review means a low-confidence guess, so check the source.

What’s next

Graph explorer

Explore what a page describes.

Memory

See what your agents remember.

Connect your agent

Add the hosted MCP at api.graphify.com/mcp. Sign in with OAuth, no API key.