Shape the review experience using the .pr_agent.toml file

You shape the review experience by combining settings in your .pr_agent.toml file. The examples below show how to tune severity thresholds, display mode, finding limits, verbosity, and ignore rules for a leaner or more verbose review.

These settings can also be configured from the Qodo portal (Recommended). See Reduce review noise on pull requests for the portal equivalent of the lean setup below, and Configure Qodo using the portal for the full settings reference.

Lean review experience

A lean review experience focuses on surfacing only the most critical issues and minimizing noise. It is typically achieved by combining:

Higher severity thresholds for inline comments
Fewer findings shown by default
Summary-focused feedback
More aggressive ignore rules (for PRs, files, tickets, or authors)

Example configuration:

# Only show the most critical issues inline
inline_comments_severity_threshold = 3

# Show feedback primarily in the summary
comments_location_policy = "summary"

# Ignore low-signal PRs and generated code
[config]
ignore_pr_labels = ["chore", "skip-review"]
ignore_language_framework = ["protobuf"]

# Display a minimal set of findings and keep most sections collapsed
# ⚠️ Not supported on Bitbucket Data Center
[review_agent_ux]
finding_overflow_count = 1
resolved_overflow_count = 1
expand_description = true
expand_code = false
expand_evidence = false
expand_prompt = false

This setup highlights only issues that must be addressed before merging and keeps the review output compact.

Verbose review experience

A verbose review experience provides broader coverage and richer context. It is typically achieved by combining:

Lower severity thresholds for inline comments
More findings shown by default
Feedback shown both inline and in summary
No ignore rules

Example configuration:

# Show multiple severity levels inline
inline_comments_severity_threshold = 1

# Show feedback both inline and in summary
comments_location_policy = "both"

# Display more findings and expand contextual sections
# ⚠️ Not supported on Bitbucket Data Center
[review_agent_ux]
finding_overflow_count = 5
resolved_overflow_count = 5
expand_description = true
expand_code = true
expand_evidence = true
expand_prompt = true

This setup is useful during onboarding, when working with new codebases, or when teams want deeper insight and guidance.

For configuring which commands run automatically per git environment, see Configure using .pr_agent.toml.

⌘I

Understand your review output

Interact with Qodo in your pull request

Customize review output

Customize review behavior

Enrich your pull request reviews

Shape the review experience using the .pr_agent.toml file

Lean review experience

Verbose review experience

​Lean review experience

​Verbose review experience

Lean review experience

Verbose review experience