Configuration File

The configuration file allows you to customize how Qodo behaves during code reviews. It controls review behavior, feedback presentation, automation, and feature-level settings.

An example configuration:

[github_app][gitlab][bitbucket_app][bitbucket_server][azure_devops_server]
pr_commands = [
    "/agentic_describe",
    "/agentic_review"
]

[review_agent] 
# "both" mode is too noisy, keep in "summary" mode in this repo
comments_location_policy = "both" 

# severity threshold rank for inline comments: 
# 3=action_required, 
# 2=remediation_recommended, 
# 1=informational. 
# Only findings with rank >= threshold will be published inline
inline_comments_severity_threshold = 3

# Extra prompt for usecase to be added as instruction for the agent 
issues_user_guidelines = ""
compliance_user_guidelines = ""

How the configuration file works

Qodo reads configuration from a file named:

pr_agent.toml

This file can exist in several locations, depending on how broadly you want the settings to apply. When a setting is defined in multiple locations, the highest-precedence configuration takes effect.

Configuration is organized into sections (TOML tables). Each section controls a specific aspect of Qodo’s behavior during code review.

Wiki configuration

Platforms supported: GitHub, GitLab, Bitbucket Cloud, Azure DevOps

How to create a wiki configuration

1. Enable the repository wiki. (Learn how here.)

2. Create a new wiki page named pr_agent.toml. Ensure the page begins with a fenced TOML block:

3. Add any configuration parameters you need.

4. Save the page.

Changes take effect immediately and do not require a repository commit.

Local repository configuration

Platforms supported: GitHub, GitLab, Bitbucket, Azure DevOps

How to create a local configuration file

1. Create a file named pr_agent.toml.

2. Add the desired configuration settings.

3. Commit the file to the root of the default branch.

The configuration takes effect for pull requests created after the change is merged.

Global organization configuration

Platforms supported: GitHub, GitLab Cloud, Bitbucket Cloud

How to create a global configuration file

1. Create a repository named pr-agent-settings in your organization.

2. Add a pr_agent.toml file to the root of the default branch.

3. Define organization-wide defaults.

The configuration takes effect for pull requests created after the change is merged and applies to all repositories in the organization unless overridden by a local or wiki configuration.

Project or group-level configuration

Platforms supported: GitLab, Bitbucket Data Center, Azure DevOps

How to create a project or group configuration

1. Create a repository named pr-agent-settings within:

• A project (Bitbucket, Azure DevOps), or

• A group or subgroup (GitLab).

1. Add a pr_agent.toml file to the root of the default branch.

2. Define the configuration settings.

This configuration applies to all repositories directly under that project or group.

GitLab: For repositories nested in multiple subgroups, Qodo looks only one level up for a pr-agent-settings repository.

Organization-level configuration (enterprise environments)

Platforms supported: Bitbucket Data Center, Azure DevOps

How to create organization-level configuration

1. Create a project named:

• PR_AGENT_SETTINGS with project key PR_AGENT_SETTINGS (Bitbucket Data Center), or

• pr-agent-settings (Azure DevOps).

1. Inside that project, create a repository named pr-agent-settings.

2. Add a pr_agent.toml file to the repository.

All repositories in the organization inherit settings from this configuration.

If both organization-level and project-level configurations exist, project-level settings take precedence. A repository’s local configuration always overrides both.