Skip to main content
Verbosity settings control where Qodo’s findings appear on your pull requests: route each severity tier (High, Medium, and Low, by default) to a different location.
High, Medium, and Low are the default severity labels, renamed from the portal using the Severity terminology setting. The examples on this page use the default names; the underlying .pr_agent.toml keys (action_required, remediation_recommended, informational) don’t change when you rename the labels. See Configure Qodo using the portal.
To control how many findings show before collapsing behind a View link, see Findings visible per group in Configure Qodo using the portal. That setting replaces the older View more control, which no longer exists in the portal.

​
Route findings by severity

By default, every severity tier appears in the same place. Use Advanced comment routing overrides to change where findings go:
  • Leave it off to keep every severity tier in the same default location.
  • Turn it on to set a different destination per severity tier, using the routing matrix.
In the routing matrix, there’s a row for each severity tier (High, Medium, and Low by default). Select one destination per row:
  • Inline: Findings appear directly on the relevant lines of code.
  • Summary: Findings appear in the summary comment.
  • Both: Findings appear both inline and in the summary comment.
  • Drop: Findings are not shown.
Navigate to Configurations > Display > Comments > Advanced comment routing overrides. See Configure Qodo using the portal.

​
Set using .pr_agent.toml

​
Action level routing mode

​
Per-severity routing

Set a nested table under [review_agent.comments_routing], with a row for each severity tier:
Avoid setting action_required to drop. High-severity findings are meant to always stay visible, and while Qodo doesn’t block this if set directly in .pr_agent.toml, it isn’t a supported configuration. For a worked example that combines these settings, see Reduce review noise on pull requests.