Configure severity levels and inline comment thresholds in pull requests

GitHubGitLab

Findings are categorized by severity. Severity is used both for prioritization and for controlling which findings appear inline in the pull request.

Configure severity thresholds

[review_agent]
inline_comments_severity_threshold = 3

Threshold Value	Inline Issues Shown	Description
Unset (default)	Not set	No threshold applied, the per-severity routing is the sole control
3	High	Blocking or critical issues
2	High, Medium	Important but non-blocking issues, plus critical ones
1	High, Medium, Low	All findings

The severity threshold applies only to inline comments.
A finding below the threshold still appears in the summary, it’s never dropped entirely.

Anatomy of a Qodo Code Review: The parts of the review comment and how to read them.
Control review verbosity in pull requests: Route each severity’s findings to inline comments, the summary, or both.
Customize the code review experience: What you can configure, and where to configure it.