The project wiki is a set of pages built from the code map. It is private to your team and read-only. Because the code map holds paths and declarations and never source text, a wiki page holds only those too.
What a page holds
There is one page for each top-level package or app, and an overview. Each page shows:
- how many files it has, in which languages, and how many declarations;
- its entry points, such as
src/index.tsormain.pyat the top of the package; - its main symbols: the top-level declarations of the entry points, or of the largest files when the entry points only re-export;
- what it depends on and what uses it, counted from the references in the code map;
- the files it was built from and the commit of the code map snapshot.
The same snapshot always gives the same pages. No model writes or edits them.
When it is built
The wiki is rebuilt when a new code map snapshot of the main line is published, and the previous wiki is removed. A snapshot of another branch does not change it. Until the first snapshot is published, the wiki says it has no pages yet.
Read it
From a terminal or an agent:
overlane wiki list
overlane wiki show overview
overlane wiki show packages-cli --jsonAgents can also call the wiki MCP tool (list, or show with a page name), and the web app shows the wiki on the project’s page. The REST routes are GET on /v1/tenants/{tenantId}/projects/{projectId}/wiki for the page list and GET on /v1/tenants/{tenantId}/projects/{projectId}/wiki/{slug} for one page. Reading needs the same access as reading the project.
Turning it off
The wiki follows the code map’s wiki setting. When it is off nothing is generated, and every read answers with status 409 and the plain message that the project wiki is turned off for the team.