Generate Repository Wiki

RepoWiki analyzes a code repository and generates structured Wiki documentation through the qoder wiki command.

Prerequisites

Complete sign-in and authentication. You can sign in through qoder or set QODER_PERSONAL_ACCESS_TOKEN. For details, see Sign-in and Authentication.
Ensure that your machine can access Qoder services. The first run prepares the required Wiki component, and Wiki generation requires network access.

Quick Start

Run the following command in the root directory of the target repository:

qoder wiki

On the first run, Qoder CLI automatically prepares the required component before starting Wiki generation. On subsequent runs, it checks the officially supported version and updates the component when necessary. No separate installation or update command is required.

Common Options

# Generate a Wiki for a specific repository
qoder wiki --repo /path/to/repo

# Generate English and Chinese documentation
qoder wiki --language en,zh

# Generate a Wiki for a specific branch
qoder wiki --branch develop

# Discard reusable Wiki data and regenerate from scratch
qoder wiki --regenerate

Option	Description
`--repo <path>`	Target repository path. Specify this option multiple times to process multiple repositories.
`--language <languages>`	Comma-separated output languages, such as `en,zh`.
`--branch <branch>`	Git branch to process. If omitted, the current `HEAD` branch is used.
`--regenerate`	Regenerate from scratch. Existing reusable Wiki data is deleted.
`--help`	Display the options supported by the installed Wiki component.

Options after wiki are passed to the Wiki component. Run qoder wiki --help to view the options supported by the current version.

Specify the Working Directory

By default, RepoWiki uses the current working directory. To select another workspace at the Qoder CLI level, place --cwd or --workspace before wiki:

qoder --cwd /path/to/repo wiki
qoder --workspace /path/to/repo wiki

You can also place --repo after wiki to select one or more target repositories.

Network and Proxy

Qoder CLI forwards common proxy and certificate environment variables when running RepoWiki, including HTTP_PROXY, HTTPS_PROXY, ALL_PROXY, NO_PROXY, and NODE_EXTRA_CA_CERTS. If component preparation, automatic update, authentication, or Wiki generation fails in a restricted network environment, verify the proxy and certificate configuration. For details, see Network, Proxy, and VPC Issues.

FAQ

Why is qoder wiki unavailable? Update Qoder CLI to the latest version, verify network access, and run qoder --help again. Why did authentication fail? Ensure that you are signed in or that QODER_PERSONAL_ACCESS_TOKEN is set correctly. For details, see Sign-in and Authentication Issues. Why did component preparation or automatic update fail? Check your network, proxy, and certificate settings, then run qoder wiki again. If a usable version is already installed, Qoder CLI can continue using it when the version check is temporarily unavailable. How do I update the Wiki component? Run qoder wiki. Qoder CLI checks and applies the officially supported version automatically. How do I rebuild an existing Wiki from scratch? Run qoder wiki --regenerate. This removes existing reusable Wiki data before generation.

Data Security

When you run qoder wiki, RepoWiki generation runs on your local machine: it launches multiple Agents locally to handle task planning, code retrieval, documentation structure planning, and similar work. Agents only read the files in your repository that the task requires.

No full-codebase upload: your complete codebase is never uploaded to the cloud during generation.
No server-side retention: your code is not stored on the server; generated results are saved only in your local repository.
Explicit trigger only: the Wiki is generated only when you run the qoder wiki command; it never runs in the background.

Next Steps

Sign-in and tokens: Sign-in and Authentication.
Network and proxy configuration: Network, Proxy, and VPC.
Command-line startup arguments: CLI Commands and Parameters.