BetaMulti-tenantSingle-tenant
Repository relationships define which repositories depend on each other. Once defined, Qodo automatically uses them to detect breaking changes across repositories when a pull request (PR) is opened. This runs by default; to view or change it, go to Configurations > General review and use the Cross-repo context toggle.
Prerequisites
- Repositories must be installed using the Qodo installation wizard. Repositories installed using a previous method will not appear until reinstalled. See the migration guide for your Git provider.
Where to manage relationships
The Repositories page has two entry points for managing relationships:- Relationships tab: View and manage all relationships across your organization.
- Repository sidebar: View and manage relationships scoped to a specific repository.

View all relationships
- Go to the Repositories page and select the Relationships tab.

View relationships for a specific repository
- Go to the Repositories page and select the Repositories tab.
- Click the row of the repository you want to inspect.
- The sidebar opens on the right. The Cross repository relationships section shows all relationships defined for that repository, including the linked repository, relationship type, description, and status.

Add a relationship
You can add a relationship from the Repositories tab by opening a repository’s sidebar.Relationships are non-directional. The order of Repository A and Repository B does not affect how the agent uses the relationship.
- Go to the Repositories page and select the Repositories tab.
- Click the row of one of the repositories to open its sidebar.
- In the Cross repository relationships section, under Add related repositories, select the Select repositories to create a relationship field.
- Select the repositories to link. Each repository supports up to 10 relationships.
- Click Add relationships.

| Status | Description |
|---|---|
| Pending | Qodo is analyzing the repositories and building the relationship context. This typically takes a few minutes. |
| Active | The relationship is confirmed and in use. Qodo checks this relationship on every relevant PR. |
| Not found | Qodo could not determine a connection between the two repositories. You can add custom instructions to guide the analysis and retry. See Retry a relationship connection. |
| Error | Something went wrong during processing. Retry the relationship connection from the three-dot menu, or delete and recreate it. |
For a description of each relationship type, see Cross-repository code review.
Retry a relationship connection
If a relationship shows Not found or Error, Qodo could not establish the connection on its own. You can provide additional context to guide the analysis and retry:- Click the three-dot menu on the relationship.
- Select Retry with custom instructions.
- In the Retry with custom instructions dialog, describe the dependency between the two repositories. These instructions give the agent additional context to guide the relationship analysis.
- Click Retry.

Remove a relationship
From the Relationships tab
- Go to the Repositories page and select the Relationships tab.
- Click the three-dot menu on the relationship you want to remove.
- Select Delete relationship.
- In the confirmation dialog, click Delete relationship to confirm.
From the repository sidebar
- Go to the Repositories page and select the Repositories tab.
- Click the row of the relevant repository.
- In the sidebar, click the three-dot menu on the relationship you want to remove.
- Select Delete.
- Confirm the deletion.
Export relationship details
Each relationship has a markdown file that describes the dependency in detail. To download it, click the three-dot menu on any relationship and select Download markdown. Use this to review what Qodo has inferred about the relationship or to share it with your team.Next steps
- To understand how Qodo uses relationships to detect breaking changes, see Cross-repository code review.
- To view and manage your repositories and installations, see Manage code review across repositories.