AI Agent - Aug 1, 2026

Qoder Knowledge Engine 2.0: Knowledge Cards vs. RepoWiki

Quick Answer

Qoder uses two related outputs for repository knowledge. Knowledge Cards are compact units designed for the coding Agent to retrieve, while RepoWiki is structured documentation designed for people to browse. They are generated together and can inform each other, but they solve different reading and retrieval problems.

Use Knowledge Cards for architecture, conventions, setup commands, specifications, and tech-stack facts that the Agent should recall. Use RepoWiki when a developer needs a navigable explanation of modules, relationships, and implementation details.

The Architecture

SurfacePrimary readerBest forMain review risk
Knowledge CardsQoder AgentDense, retrievable project factsIncorrect or stale facts silently steering work
RepoWikiDevelopers and reviewersBrowsable repository documentationPolished pages hiding missing scope or wrong interpretation
Conversation MemoryQoder Agent and team knowledge flowDecisions, pitfalls, and experience from conversationsTemporary discussion becoming durable policy

Qoder’s documentation calls Knowledge Cards “high-density” units extracted from code and describes RepoWiki as automatically generated structured project documentation. The provider says these surfaces can improve context, but teams should measure their own accuracy and accepted-work outcomes.

How Generation Works

Qoder recommends generating knowledge on the main branch and frequently used development branches. The system analyzes the repository and creates RepoWiki and Knowledge Cards together. Completed cards can be previewed while generation continues.

Generation is not the end of the workflow. Reviewers should check:

  • architecture boundaries and module ownership;
  • setup and test commands;
  • public APIs and known exceptions;
  • security-sensitive paths;
  • generated links to code;
  • branch and commit used for the analysis.

Record the branch and review date in the acceptance notes. “Continuously updated” is a product mechanism, not proof that every card is current.

Human Intervention

Qoder documents two control paths:

  1. /knowledge can generate, modify, supplement, or rewrite RepoWiki and Knowledge Cards.
  2. /knowledge-plan creates or edits wiki_plan.yaml, which can guide templates, notes, document allowlists, and include or exclude scope before generation.

Use the configuration file when the repository is too large or when specific paths must be excluded. Treat manual edits as reviewed knowledge: assign an owner, explain why the change is correct, and make sure the next code change does not invalidate it.

Sharing Options

Qoder documents two sharing paths:

  • Teams can use the Enterprise Knowledge Engine after an administrator enables team collection.
  • Repositories can share the generated .qoder/repowiki directory through Git.

Those paths have different governance implications. Cloud team sync centralizes knowledge by repository and branch. Git sharing places generated knowledge in version control, where normal review, retention, and branch policies can apply.

The enterprise Wiki CLI and security guide compares local generation, Git sharing, and managed team sync. The Qoder product guide explains current access and product boundaries.

An Acceptance Test

Evaluate one repository with 20 questions that have known answers:

  1. five architecture questions;
  2. five setup or command questions;
  3. five code-convention questions;
  4. five recent-change questions.

Run each question with and without the generated knowledge. Measure correct answers, unsupported answers, source-location accuracy, correction time, and credit or latency changes. Review the RepoWiki separately for navigation, missing modules, stale pages, and developer comprehension.

The useful result is not “more documentation.” It is fewer repeated investigations and fewer accepted errors.

FAQ

Are Knowledge Cards the same as RepoWiki pages?

No. Knowledge Cards are compact units optimized for Agent consumption; RepoWiki is structured documentation for people. Qoder generates them together and allows knowledge changes to flow between them.

Does Qoder update knowledge automatically?

Qoder documents code-change detection and commit-linked updates. Teams should still review branch scope, recent changes, and critical facts before trusting generated knowledge.

Can a team edit generated knowledge?

Yes. Qoder documents /knowledge for modifying, supplementing, or rewriting knowledge and wiki_plan.yaml for controlling generation scope and direction.

Can Knowledge Cards be shared through Git?

Yes. Qoder stores generated content in .qoder/repowiki, which can be committed and pulled through the team’s normal Git workflow. Review generated changes before merging them.

Official Sources

Source check: August 1, 2026. Verify the live Qoder client, plan, and documentation before rollout.