Skip to content

14 repos · one private workspace

One private wiki for every repo's docs.

RepoWiki brings documentation from all your repositories into one shared workspace, so PMs, developers, and agents can read, search, and trust the same project context.

Create workspaceView overview

Source identity

synced 2m ago

Repos indexed

14

Branch

main

Source path

docs/architecture.md

Commit

a18f3c9

Readers always see the repository, branch, path, commit, and sync state behind a page.

RepoWiki

product-suite / main

synced
ProductSuite/platform-web/docs/architecture.md

Architecture overview

Last synced from source branch main @ a18f3c9. Source details stay attached.

RepoWiki indexes committed docs by workspace, project, repository, path, branch, and file hash. The workspace becomes the private reader; the source stays attached for review and confidence.

Reader contract

Every page keeps repository, source branch, path, commit, and hash visible.

Search results resolve to verified reader pages teams can share.

Sync history explains what changed without moving how teams review docs.

source

main @ a18f3c9

path

docs/architecture.md

scope

workspace

GET /projects/product-suite/repos/platform-web/docs/architecture
source: docs/architecture.md
branch: main
commit: a18f3c9
hash: sha256:6c9f...

Documentation reality

Product, engineering, and agents

why now

01 / Before

After-the-fact knowledge

The important details exist, but they arrive as translations with unclear source, timing, and ownership.

Source unclear

Engineer review needed

Context copied by hand

Wiki catches up after release

Decisions live in meetings

Code keeps moving

Source-backed context matters because readers need to know where knowledge came from, not only what it says.

Documentation reality

Product, engineering, and agents

why now

02 / Now

Source-adjacent docs

The newest docs have branch, path, commit, and behavior attached before they ever become a polished wiki page.

Architecture note from repo

Agent instructions updated

Runbook follows behavior

Commit context becomes prose

Runbooks follow behavior

Agents inherit project memory

Source-backed context matters because readers need to know where knowledge came from, not only what it says.

Documentation reality

Product, engineering, and agents

why now

03 / Required

Shared reader layer

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

Private workspace

Visible source path

Synced from main

PMs read without GitHub file trees

Developers keep Git as source

Agents retrieve current context

Source-backed context matters because readers need to know where knowledge came from, not only what it says.

Product

Repo-native docs, product-grade clarity.

RepoWiki turns scattered repo documentation into a shared workspace with the polish, navigation, and source confidence a whole team can use.

What ships

A private docs layer for reading, search, and confidence.

Across repos

Reader experience

Every connected repo becomes part of one workspace, so project knowledge stops feeling scattered.

For confidence

Trust built in

Source details stay available when they matter, without making the product feel like a code browser.

For collaboration

Shared operating memory

PMs, developers, and agents work from the same pages instead of parallel notes and stale summaries.

Workspace preview

Every page carries the confidence of its source.

indexed

Architecture overview

platform-web / main

docs/architecture.md

Webhook retry windows

billing-api / main

docs/webhooks.md

Agent context pack

codex-agents / main

AGENTS.md

Technical owners keep the source of truth. Everyone else gets a workspace they can read without losing confidence.

Collaboration

Same context. Different tools.

RepoWiki gives non-technical teammates a real reading experience while developers keep the review habits that make docs reliable.

Collect the scattered context

Bring architecture notes, runbooks, and agent docs together.

Give every team a reader

PMs and operators can browse without living in repo file trees.

Keep the proof attached

Developers keep source control while readers keep confidence.

Knowledge sources

Architecture notes
Operational runbooks
Agent instructions

Selected repos and docs

Connect the work

Choose the repos and docs that should become shared context.

Create a workspace map

Pages are organized by project, service, source, and audience.

Invite collaborators

PMs, developers, operators, and agents read from the same place.

Shared workspace

Team reader
Cross-repo search
Shared links
Source confidence

Workspace search

Find the answer faster.

Search across projects, services, runbooks, architecture notes, and agent instructions from one workspace instead of guessing which repo has the answer.

Query

webhook retry

Scope

14 repos

Source

main @ 6d42b10

Search all repo docs

42ms
webhook retry

Architecture overview

docs

platform-web/docs/architecture.md

Webhook retry windows

runbook

billing-api/docs/webhooks.md

Agent context pack

agent

codex-agents/AGENTS.md

Legacy login callbacks

stale

identity/docs/legacy-auth.md

Webhook retry windows

billing-api/docs/webhooks.md

runbook

Retries back off for transient 5xx responses, preserve idempotency keys, and surface failed delivery counts in sync history.

3 repos

8 snippets

main

branch: main
commit: 6d42b10
source: attached

Confidence

Readable for everyone. Traceable when needed.

Readers get a polished workspace; technical owners keep clear source, access, and rendering boundaries behind every page.

Know where it came from

Repository, source branch, path, commit, and sync state stay attached.

Invite the right readers

Workspace membership defines who can read private docs.

Keep boundaries clear

Selected repos and docs paths define what enters the workspace.

Source and access

Source attached

path, branch, commit, sync state

Workspace access

only invited members read

Selected scope

only chosen repos enter

Clean rendering

Markdown displayed safely

Workspace boundary

Write path

Technical owners choose which repository docs enter the workspace.

Read path

Invited teammates read polished pages without needing the repo UI.

Clean reading experience

Markdown is rendered as readable content with unsafe HTML blocked before display.

Fit

Built for knowledge spread across repos.

RepoWiki is for teams whose most important project knowledge already lives near engineering work, but needs to be readable across product, engineering, operations, and agents.

Shared private workspace

GitHub

Wiki

Docs site

Reads across many repos

GitHub

Wiki

Docs site

Polished non-GitHub reader

GitHub

Wiki

Docs site

Source confidence on every page

GitHub

Wiki

Docs site

Useful to PMs, devs, and agents

GitHub

Wiki

Docs site

Bring every repo's docs into one private workspace.

Give your team one place to understand the work.

Create workspaceSign in