Opening the page…
Forge Wiki works for private repositories without publishing their source or generated documentation.
Open the Wiki tab from a private repository just as you would for a public one. The same repository permissions apply:
Wiki URLs and immutable version links can be shared with collaborators, but the link itself does not grant access. Each request rechecks the viewer's current repository permission. Private responses are not stored in shared caches or browser caches. Public Wiki responses also revalidate through Forge so a later visibility change cannot leave a shared cached copy available.
Generation selects a bounded set of text files from one exact commit. Forge treats repository source as data and never executes it. The selected source is sent to the configured model provider to generate the Wiki, so use a provider and funding mode that meet your repository's privacy requirements.
Generated pages, search data, and citations stay in Forge's private artifact storage. They do not appear in public repository listings, anonymous Wiki search, or unauthenticated MCP responses.
MCP clients can read a private Wiki with a signed-in session or a personal
access token carrying repo:read. Asking a private Wiki with a personal access
token additionally requires wiki:ask; repository-scoped tokens must name the
same repository.
Removing a collaborator's repository access removes their Wiki access immediately. Changing a repository between public and private does not require rebuilding the Wiki; Forge applies the new repository access policy to the existing immutable artifacts. Unlisted repositories remain ineligible for Wiki access and refresh until they return to a supported visibility.
Deleting or suspending the repository blocks its Wiki immediately. Artifact retention and deletion then follow Forge's repository cleanup policy.