Skip to main content
Qodo v2 is designed to work out of the box, with minimal setup required. Teams can start receiving useful pull request feedback immediately, while configuration options allow you to fine-tune how reviews behave and how feedback appears in your workflow. Configuration settings are defined in the repository’s .pr_agent.toml file and can also be applied at the organization level in the Qodo portal. Learn more in Customize the code review experience. Commands can be used directly in pull request comments to trigger actions such as running reviews, generating summaries, or asking questions about code changes. The sections below describe the available configuration settings and PR commands you can use to tailor the Qodo review experience.

Repository configuration options

Configuration is managed in the .pr_agent.toml file.

Review output and visibility

SettingTOML sectionDescriptionValues
comments_location_policy[review_agent]Controls where findings are posted in the pull request.summary – all findings appear in a single summary comment
inline – findings are posted directly on relevant lines of code
both – a summary comment is posted and findings are also added inline (default)
inline_comments_severity_threshold[review_agent]Determines which severity levels generate inline comments.3 – action required only (default)
2 – action required and remediation recommended
1 – all findings

Findings display

SettingTOML sectionDescriptionValues
finding_overflow_count[review_agent_ux]Controls how many findings are shown before the rest collapse behind “View all”.none – all findings collapsed
1, 3 (default), 5 – number of findings shown before “View all”
all – all findings expanded
resolved_overflow_count[review_agent_ux]Controls how many resolved findings are shown before collapsing.none, 1, 3 (default), 5, all

Expanded sections in findings

SettingTOML sectionDescriptionValues
expand_description[review_agent_ux]If set to true, expands the description section by default.true (default) / false
expand_code[review_agent_ux]If set to true, expands the code section by default.true (default) / false
expand_relevance[review_agent_ux]If set to true, expands the relevance section by default.true / false (default)
expand_evidence[review_agent_ux]If set to true, expands the evidence section by default.true / false (default)
expand_prompt[review_agent_ux]If set to true, expands the agent prompt section by default.true / false (default)

Review workflow options

SettingTOML sectionDescriptionValues
pr_commandsGit provider section ([github_app], [gitlab], [bitbucket_app], [bitbucket_server], [azure_devops_server])Commands run automatically when a PR is opened or updated./agentic_describe, /agentic_review
handle_push_triggerGit provider section ([github_app], [gitlab], [bitbucket_app], [bitbucket_server], [azure_devops_server])If set to true, re-runs configured commands when new commits are pushed to the pull request.true / false (default)
demand_self_review[review_agent]If set to true, a checkbox appears in the PR for the author to confirm they reviewed the findings.true / false (default)
approve_pr_on_self_review[review_agent]If set to true, adds Qodo as a reviewer after the author confirms self-review, allowing the PR to be merged.true / false (default)
enable_chat_in_code_suggestions[pr_code_suggestions]If set to true, enables Qodo to automatically recognize and respond to questions written in PR comments.true (default) / false

CI feedback options

GitHub
SettingTOML sectionDescriptionValues
enable_auto_checks_feedback[checks]If set to true, automatically provides feedback when a CI check fails on a pull request.true (default) / false
excluded_checks_list[checks]A list of CI checks to exclude from feedback.["check1", "check2"]
persistent_comment[checks]If set to true, updates an existing CI feedback comment instead of posting a new one for each run.true (default) / false
enable_help_text[checks]If set to true, displays a help message when a user comments /checks on a pull request.true (default) / false
final_update_message[checks]If set to true, posts an additional message indicating the CI feedback was updated to the latest commit.true (default) / false

Ignore rules

Configuration keyTOML sectionDescriptionValues
ignore_pr_title[config]Ignores PRs with matching title patterns.regex list
ignore_pr_source_branches[config]Ignores PRs from matching source branches.regex list
ignore_pr_target_branches[config]Ignores PRs to matching target branches.regex list
ignore_pr_labels[config]Ignores PRs with specific labels.label list
ignore_pr_authors[config]Ignores PRs opened by specific users.regex list
ignore_repositories[config]Excludes specific repositories from analysis.regex list
allow_only_specific_folders[config]Limits analysis to PRs that touch specific folders.folder list
ignore_languages_frameworks[config]Excludes generated files by language/framework.framework list
ignore_ticket_labels[config]Ignores linked tickets with specific labels.label list

PR commands

These commands can be invoked directly in pull request comments.
CommandUseDescription
/agentic_reviewPrimary review workflowRuns the main Qodo review experience, generating prioritized findings and suggested fixes.
/agentic_describePR summarizationGenerates a structured summary of the pull request.
/askPR-specific questionsAnswers questions about the pull request and its code changes.
/configInspecting available settingsShows supported configuration keys and default values.
/generate_labelsPR categorizationSuggests pull request labels based on code changes.
/checksCI troubleshootingAnalyzes CI failures and surfaces useful debugging context.