Quick Answer
Use qodercli wiki when repository code must stay in the local environment during Wiki generation. Use Git-shared .qoder/repowiki when generated knowledge should follow normal branch and review workflows. Use the Enterprise Knowledge Engine when a Teams or Enterprise organization needs managed, branch-aware team browsing and sync.
These are different control models. Local generation minimizes the code-processing boundary; Git sharing makes knowledge versioned; managed sync simplifies team access but introduces organization, retention, and cloud-sharing decisions.
Three Deployment Paths
| Path | Code and knowledge path | Good fit | Review before use |
|---|---|---|---|
qodercli wiki | Qoder says generation runs locally and repository code is not uploaded | Restricted or local-first repositories | Tool download, authentication, binaries, output scope, local secrets |
Git-shared .qoder/repowiki | Generated knowledge is committed to a repository branch | Teams with strong code-review workflows | Generated diff, confidential text, repository access, retention |
| Enterprise Knowledge Engine | Desktop-generated knowledge syncs to managed team storage | Teams / Enterprise shared browsing and reuse | Admin enablement, member sync, branch behavior, data policy, retention |
Qoder’s CLI documentation says the Wiki command is an external command downloaded on first use. The initial download and authentication require network access, even though Wiki generation itself runs locally.
Local Wiki CLI Checklist
Before running qodercli wiki on a sensitive repository:
- Install Qoder CLI from the official source and verify the current documentation.
- Confirm authentication through sign-in or a protected personal access token.
- Review proxy, certificate, and external-command registry settings.
- Inspect the repository for secrets, regulated data, generated artifacts, and excluded paths.
- Run in a disposable branch or copy first.
- Review generated files before committing or sharing them.
Avoid bypass-style permission modes in production workflows. Qoder’s permission documentation distinguishes interactive, edit-accepting, auto, non-interactive deny, and bypass modes. The safest mode is the least permissive one that completes the approved task.
Git Sharing
Qoder stores generated RepoWiki and Knowledge Card material under .qoder/repowiki. A team can commit that directory and review changes like code.
Add governance rules:
- require reviewers who know the affected modules;
- block secrets and personal data;
- label generated changes separately from human decisions;
- keep branch-specific knowledge on the correct branch;
- define whether old generated knowledge is retained or removed;
- regenerate and review after material architecture changes.
Git history improves traceability, but it also makes accidental disclosure durable. Scan the generated diff before push.
Managed Team Knowledge
Qoder documents the Enterprise Knowledge Engine for Teams and Enterprise plans. An administrator must enable Team Knowledge Collection, which is disabled by default. The managed surface aggregates RepoWiki, Knowledge Cards, and Memory Cards by repository and branch.
The documentation also says disabling the engine pauses updates and that collected data is retained for a limited period before deletion. Verify the current retention language, backup needs, organization access, and offboarding process before enabling it.
Member sync behavior deserves testing. Qoder describes cases where cloud knowledge is pulled or overwrites local knowledge, and notes that manual /knowledge changes affect automatic sync behavior. Run a non-production branch exercise before broad rollout.
Security Does Not End at Local Generation
Even when code remains local, generated documentation can expose system design, internal endpoints, commands, credentials accidentally present in source, or security assumptions. Treat generated knowledge as sensitive as the repository it describes.
Qoder’s security scan documentation says its scanning is not a replacement for a full security audit. Use existing secret scanning, dependency checks, code review, threat modeling, and organization controls alongside any Agent feature.
For the knowledge types themselves, see Knowledge Cards versus RepoWiki. For update behavior, see the self-iterating memory guide. The Qoder product guide provides the current access map.
FAQ
Does qodercli wiki upload repository code?
Qoder’s current CLI documentation says Wiki generation runs locally and repository code does not leave the environment. First use still downloads the external Wiki tool and authentication requires network access.
Is Qoder team knowledge enabled by default?
No. Qoder says Team Knowledge Collection is disabled by default and an administrator must enable it for managed collection and sharing.
Can a team share Qoder knowledge without the enterprise sync?
Yes. Qoder documents Git sharing of the generated .qoder/repowiki directory. Review generated content and repository permissions before committing it.
Does Qoder security scanning replace a security audit?
No. Qoder explicitly says its scan is not a complete security audit. Keep independent testing, review, and organization controls.
Official Sources
- Qoder Wiki CLI
- Qoder Enterprise Knowledge Engine
- Qoder RepoWiki sharing
- Qoder CLI permissions
- Qoder CLI security scan
Source check: August 1, 2026. Confirm current plan, client, organization policy, and documentation before rollout.