Export the repo wiki

Feature Requests
1

Problem

  • Repo Wiki is excellent at auto-summarizing a codebase, but its output is only viewable inside the IDE.

  • Users cannot export/share/print the generated architecture report, making it hard to: hand off, review externally, archive, or include in documentation.

  • Current workflow forces manual copy/paste or screenshots — slow, error-prone, and lossy.

Solution

Add a first-class Export Repo Wiki feature that produces shareable, portable reports from the repo wiki. Key capabilities:

  • Export formats: Markdown (single file or folder), PDF, HTML (standalone), JSON (structured), and ZIP bundle (Markdown + assets).

  • Scope & filters: choose whole wiki, selected sections, or custom page range; include/exclude code samples, binary assets, and diagrams.

  • Output targets: direct download, save to workspace, commit to a branch / create PR, or upload to a gist/cloud link.

  • UI & CLI: button in the wiki UI + Command Palette entry + ide export-wiki CLI command.

  • Preserves formatting: code blocks, tables, anchors, images; generates TOC and metadata (repo, branch, generation date, generator version).

How should it work?

  1. In repo wiki view click Export (or run Cmd/Ctrl+Shift+P → Export Repo Wiki / ide export-wiki).

  2. Modal options:

    • Format: Markdown / PDF / HTML / JSON / ZIP

    • Scope: Entire wiki / current section / selected pages

    • Include: code snippets, images, commit links, full file paths, license header

    • Output: Download / Save to workspace / Commit & PR / Shareable link

    • Branding: light/dark theme, company header/footer (optional)

  3. User clicks Generate → progress indicator (streaming for large exports).

  4. Preview (for HTML/PDF) then Download or Save.

  5. Completed export shows link to file location + quick action buttons (open folder / create PR / copy link).

Use Case

  • Share a concise architecture & API overview with non-technical stakeholders.

  • Prepare documentation for onboarding new developers.

  • Attach architecture report to tickets, audits, or client deliverables.

  • Archive a snapshot of repository structure and API docs before refactor.

When would you use this?

  • Pre-demo or client handoff.

  • Code reviews / architecture reviews.

  • Team onboarding sessions.

  • Security or compliance audits.

  • Offline reading or printing.

Priority

:red_circle: High — Blocking issue
Rationale: Without export, the wiki’s value is limited for sharing and archiving. Export unlocks most real-world uses (review, handoff, compliance).

4 Likes
2

any news on this? it is kinda mandatory feature

3

Yeah, it doesn’t make sense that they have access to train their ai using a wiki repo that was generated using your code, but you can’t access it, I wonder if any other ai ide’s do this but in the background without you knowing :thinking:

4

YES please we need this !! <3

5

Please let us extract the repo wiki to markdown for quick context engineering ! thanks

6

希望支持MarkDown格式的仓库wiki导出

7

This feature is already in the works, so stay tuned!

10 Likes
8

Problem

Many legacy repositories contain legacy code that couldn’t simply use ignore files.

Solution

Make repo wiki indexing follow the Qoder rules to ignore them during indexing.

Use Case

Studying large legacy codebase

Priority

Important improvement

Additional Info

I think this is very important as repo wiki is an important feature compared to other AI tools like Cursor, Kiro and etc.

9

I found I cannot watch generated wiki repo under NO INTERNET enviroment. It is very unconvinent for research and study,beacuse research needs FOCUS. So I wonder is it possibile export the wiki repo to my local disk or open the privilege to watch under no internet environment? Thanks!

2 Likes
10

Problem

Allow us to export repo-wiki or upload the repo-wiki to the cloud so that we can cross machine coding. And the repo-wiki can be shared with other teammates

Solution

A button allow us export the repo-wiki, or upload the repo-wiki to cloud

Use Case

Every time onboarding a new machine

Priority

  • :red_circle: High - Blocking issue
  • :yellow_circle: Medium - Important improvement
  • :green_circle: Low - Nice to have

Additional Info

(Optional: screenshots, examples, links)

1 Like
11

Wiki 功能目前看下来整体是非常棒的，但是存在几点问题希望能够改进或者提供纠正功能：

  1. 有些在理解上可能有点错误
  2. 有些 Mermaid 图示无法显示
  3. 有些则是关联出了点问题（关联到不相关的东西）
1 Like
12

I have a temporary export plugin built by kiro.dev and then fixed by claude code.
I say temporary because I will delete the repo when the official Qoder export functionality ships.

Clone it, package it, install it. Enjoy !

Qoder team feel free to use anything from this repo if you find it useful.

4 Likes
13

It would be great if there was a way to automatically execute repowiki via the CLI.

14

Amazing work ! I like it!

1 Like
15

Too slow to generate repowiki! And always pending for some hours!

image
image590×830 35.3 KB

16

Amazing work! I really like it :clap::fire: I tested it and it works great!

17

good this ，we need this :rofl: