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. For more information, 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, both inline and in the summary comment. Use Publishing locations to change where findings go:
  • Inline & Summary, Inline, or Summary: Every severity tier goes to that location.
  • Mixed: The severity tiers go to different locations, set in the routing matrix. Publishing locations shows Mixed whenever the rows differ.
In the routing matrix, there is a row for each severity tier (High, Medium, and Low by default). When Group by is set to another grouping, such as Finding type, the matrix rows follow that grouping instead. Select one destination per row:
  • Inline: Findings appear directly on the relevant lines of code.
  • Summary: Findings appear in the summary comment.
  • Inline & Summary: Findings appear both inline and in the summary comment.
  • None: Findings are not shown.
When the rows follow severity, the High row cannot be set to None, so high-severity findings always appear in at least one place. With another grouping, such as Finding type, any row can be set to None, and Qodo then leaves out every finding in that row, including high-severity ones. How saving works:
  • The routing matrix always shows where Qodo publishes each row.
  • Selecting a display mode or changing a single row saves every row of the matrix.
  • Rows you did not touch keep the location shown.
Selecting a display mode on the Display tab also sets the routing matrix: When a repository or Git organization changes any row, it saves its own copy of the whole matrix. Later changes at the workspace level then do not change its routing. To follow the workspace again, reset the repository or organization to the workspace settings, which clears every row at once.
  1. Log in to the Qodo portal.
  2. Navigate to Configurations > Display > Comment routing.
  3. Under Publishing locations, choose where findings go:
    • Select Inline & Summary, Inline, or Summary to send every row to the same place.
    • Set each row’s destination in the routing matrix to route the rows separately.
  4. Click Save changes.
For more information, see Configure Display settings in the Qodo portal.

​
Configure review verbosity in .pr_agent.toml

​
Action level routing mode

comments_routing_preset is unset by default (the key is commented out in configuration.toml). Set it explicitly to control every severity tier the same way:
When more than one of these settings is present, Qodo resolves them in this order: [review_agent.comments_routing] table > comments_routing_preset > comments_location_policy.

​
Per-severity routing

Set a nested table under [review_agent.comments_routing], with a row for each severity tier. comments_routing_preset doesn’t need to be set to "custom" for this table to take effect. An unset preset with this table defined works the same way.
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.