Configuration Fundamentals

This guide explains how to configure Qodo’s code review experience so it matches your team’s standards, workflows, and tolerance for noise.

You don’t need to configure everything to get value from Qodo. Most teams start with the defaults and selectively customize only what they need.

Configuration allows you to:

• Filter out noise from irrelevant pull requests

• Guide Qodo’s feedback to align with your team’s practices

• Maintain consistent review behavior across projects and repositories

• Improve the quality, relevance, and focus of review feedback

What can you configure?

Qodo configuration allows you to control several aspects of the review experience, including:

• How reviews run

  • Which review commands are available

  • Whether reviews run manually or automatically

  • When reviews run (for example, on PR open or update)

• How feedback appears

  • Summary vs inline comments

  • Severity thresholds for inline feedback

  • Limits on the number of surfaced findings

• What Qodo reviews

  • Which repositories, branches, folders, or files are included

  • Which pull requests should be ignored

  • Which tickets or labels should be excluded

• How Qodo behaves

  • Custom instructions for review output

  • Persistent review comments

  • Feature-level behavior (for example, suggestion tracking or CI feedback)

How to set configuration

All Qodo configuration is defined using a file named:

pr_agent.toml

This file can be defined at different levels, depending on how broadly you want settings to apply.

Local configuration (repository-level)

Place a pr_agent.toml file in the root of a repository.

• Applies only to that repository

• Settings take effect for pull requests created after the file is added

Global configuration (organization-level)

Create a repository named: pr-agent-settings

Add a pr_agent.toml file to that repository.

• Acts as a default configuration for all repositories in the organization

• Can be overridden by local or wiki configuration

Wiki configuration

Create a pr_agent.toml page in the repository’s wiki.

• Does not require committing changes to the codebase

• Easy to update at any time

Configuration precedence

When configuration is defined in multiple places, Qodo applies settings in the following order:

1. Wiki configuration (highest precedence)

2. Local repository configuration

3. Global organization configuration (lowest precedence)

This allows teams to define shared defaults while still supporting repo-specific overrides when needed.