Skip to content

One private workspace for repo docs and source-backed AI answers.

RepoWiki turns committed documentation into a readable library. Lens asks across that library with citations, while approved MCP clients use the same scoped context.

Source-backed AI

Lens asks the workspace with citations

Citations

Open the docs behind every answer

MCP clients

Give approved tools the same context

Why now

Documentation moved closer to the work. Reading did not.

RepoWiki exists because the newest project context now starts in repos, commits, and agents, but the team still needs one trusted place to read it.

01 / Before

Docs used to lag behind the work.

For years, product context was reconstructed after the work happened: copied from tickets, meetings, releases, and engineering memory into a separate tool.

Source unclearEngineer review neededContext copied by hand

02 / Now

The freshest docs are born closer to code.

Agents now turn commits, PRs, repo files, and runtime behavior into specs, runbooks, architecture notes, and durable instructions.

Architecture note from repoAgent instructions updatedRunbook follows behavior

03 / Required

The team needs a shared reader.

The new bottleneck is not typing more pages. It is giving PMs, developers, and agents one trusted place to read verified context together.

Private workspaceVisible source pathSynced from main

Outcome

Shared reader layer

The team needs a reader that preserves source detail while making the work legible outside the repository.

PMs read without GitHub file trees
Developers keep Git as source
Agents retrieve current context

Product

Repo docs become shared context.

Keep docs in Git. RepoWiki turns selected Markdown, MDX, runbooks, and agent instructions into one private workspace for teammates, the Lens preview assistant, and approved MCP clients.

Repo sources

Git remains source
platform-webdocs/architecture.mdin scope
billing-apidocs/webhooks.mdrepo
codex-agentsAGENTS.mdrepo

RepoWiki workspace

One indexed library for people, Lens, and approved clients.

1Selectrepos
2Indexsource
3AskLens
4Servereader + clients

Architecture overview

platform-web/docs/architecture.md

source attached

Webhook retry windows

billing-api/docs/webhooks.md

synced 2m ago

Agent context pack

codex-agents/AGENTS.md

read-only

Destinations

scoped access

Team reader

PMs, developers, operators

Search, read, verify source

Lens preview

Workspace members

Ask with citations and source scope

MCP clients

Approved tools

Read-only search and fetch

Selected docs become one workspace, with source details attached.workspace.search to docs.read

Lens preview

Ask the workspace. Open the source.

Lens answers from indexed workspace docs, shows cited files, and stays read-only. Narrow the question to a project or the full workspace.

Scoped

Ask one project or the whole workspace

Cited

Answers keep the source files close

Read-only

Lens cannot edit docs or change settings

Workspace Lens

ProductSuite workspace

preview
ProjectWorkspace

Your question

What changed in webhook retry behavior?

Lens answer

The retry window moved from a fixed retry note to a backoff policy tied to event delivery. The current docs point readers to the webhook runbook and architecture path before changing client behavior.

matched

4 docs

read

2 files

cited

2 files

Cited files

1

Webhook retry windows

billing-api/docs/webhooks.md

main @ 6d42b10

2

Event delivery path

platform-web/docs/architecture.md

main @ a18f3c9

Run trace

Search · webhook retry across workspace

Read · 2 source files opened

Answer · citations attached

MCP server

Let approved clients read the same source-backed context.

MCP gives supported clients scoped retrieval from the same workspace people and Lens use. Approved clients can search and read source-backed docs with structured responses, without copying pages into prompts or giving tools write access.

Explore MCPSetup guide

Workspace endpoint

/api/mcp/w/product-suite

client request

search_docs({
  query: "webhook retry",
  limit: 5
})

Token scoped to workspace

No writes exposed

Usage recorded

source-backed response

read-only

billing-api/docs/webhooks.md

Retry windows and backoff rules

platform-web/docs/architecture.md

Event delivery path

codex-agents/AGENTS.md

Agent-safe instruction source

RepoWiki returns structured content with project, repository, branch, path, and commit still attached. The same JSON remains available as text fallback.

Read-only

Search and read docs only

Source-backed

Project, repo, branch, path

Structured

JSON fallback for clients

Metered

Team beta with usage limits

The missing layer

Not another wiki. Shared context for docs already in Git.

GitHub keeps source and review. Wikis and docs sites help teams write and publish. RepoWiki makes repo knowledge interactive: teammates search it together, share current pages, ask Lens with citations, and give approved MCP clients the same source-backed context.

GitHub

Source and review

docs change beside code

Wikis

Blank-page writing

notes live in another system

Docs sites

Public-facing docs

finished guides for one product or API

RepoWiki

Shared context layer

people, Lens, and MCP clients use the same source-backed docs

Start with the docs you already have.

Create your shared docs workspace.

Keep source in Git. Give teammates, Lens, workspace search, and approved MCP clients one trusted place to use it.

Create workspaceSign in