​

Multi-project routing

One GitHub repo can be connected to multiple Qodex projects. Use this only when different teams need independent review policies, findings, and project memory for the same codebase.

​

How it works

When a PR event fires on a repo connected to two projects, Qodex runs one review per project. Each project posts its own walkthrough comment, inline findings, and Check Run. Findings, spend, memory, and custom skills stay separate. The projects do not see each other’s reviews. To make the two checks easy to tell apart in the GitHub UI, the Check Run name carries the project slug as a suffix. What stays shared:

• .qodex.yaml (it lives in the repo).
• The GitHub events and the PR diff itself.

What is per-project:

• Findings, spend, and any custom skills.
• The Check Run identity in GitHub.

​

When this is useful

Use multi-project routing when two teams genuinely need independent reviews on the same code. For example, a security team and a product team may want different memory, skills, severity thresholds, and gate policies.

​

When this isn’t useful

Do not link the same repo to multiple projects just to “double-check” the review. That creates duplicate LLM spend and makes the PR thread noisy. One project per repo is the right default.

​

Related