Wiki

Wiki is the written documentation for one repository. Open Engineering Context Graph, then Wiki, or go to /code-chat/wiki, and choose a repository.

What an index does

Starting an index, or choosing to write pages, runs for that repository only. Other repositories keep their current status.

The work is one pass:

1. Download the default branch.
2. Build the code map.
3. Write the pages in groups.

While pages are being written, the status names the group in the current step and how many pages that step includes. Earlier pages stay saved. The count is the size of the current step, not a shrinking total for the whole wiki.

A repository that has never been indexed shows the same in-progress message as soon as the index starts. It does not stay on “not indexed yet” while the job is queued or running.

If a write stops updating for several minutes and the job is still running, Continue resumes it. A job that is only queued shows Restart, not Continue. Do not continue a write that is still moving. That drops the live job.

What the pages contain

Typical pages include an overview, architecture, how the repository is structured, the API surface when one is detected, and the data model when one is detected. Links inside a page open the related wiki page or the context graph. A link that names another repository in this workspace opens that repository.

The page text does not name the internal writers or diagram tools. What you read is the repository’s own structure and the prose written from it.

Writing pages

Use the workspace execution key. Any key the workspace already uses for agent work can write the pages. You do not need a separate key brand.

Download and rebuild the code map stays on for a page write, because the write needs that download.

A full write on a large repository takes a long time. The status line is the source of truth for which step is running.

Download

Download on a repository wiki saves the written pages. Use it when you want to hand the repository context to another model. Links that point at a GitHub file use the repository’s GitHub address when the source is GitHub.

Limits

• Page quality follows the index. Very small indexes are not treated as a full product description.
• A shared filename, or an id that is only a number, is not a call from one repository into another.
• The product does not invent delivery metrics or person-level AI usage.

Related

• Engineering Context Graph
• Workspace: the picture across repositories
• Code Insights: quality metrics from readiness, separate from the wiki