01 / collect
Start where the docs already live
Bring in the Markdown, MDX, runbooks, decision notes, and agent instructions your team already maintains in GitHub.
Docs / guide
Make repo docs readable for the whole team.
RepoWiki turns the docs already spread across your repositories into one private workspace for reading, search, and shared context.
Details
From repo files to shared context.
The core workflow is simple: connect the right docs, keep the workspace private, make answers searchable, and keep source details available when readers or Lens need proof.
02 / sync
Choose what enters the workspace
Choose the repositories and docs paths that belong in the workspace. RepoWiki keeps the source trail available without turning every page into a file viewer.
03 / read
Give the team one reader
Readers browse by project and search across the workspace without guessing which repo has the answer.
04 / Lens
Ask the workspace with citations
Lens preview answers from indexed workspace docs with citations, durable threads, scopes, and usage limits. It stays read-only and source-backed.
05 / MCP
Connect MCP clients
Team workspaces can expose read-only MCP tools for source-backed search and document reads, with structured responses, JSON text fallback, and hosted-connector OAuth.
06 / safety
Keep sensitive material out
Use private workspaces for project knowledge. Keep secrets, credentials, and regulated data out of docs, even when access is limited.
workspace snapshot
Proof stays close to the page.
Every page should answer three questions without making readers work for them: where it came from, when it changed, and who can read it.
Source
Selected repos · docs/ · main
Content
Markdown and MDX
Details
repo, branch, path, commit
Boundary
private workspace members