> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qodo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Control findings visibility and expansion in pull requests

> Configure how many findings are shown, collapsed, or expanded in pull request reviews to keep feedback focused without losing full visibility.

export const GerritIcon = () => <svg className="gerrit-icon" viewBox="0 0 52 52" width="12" height="12" style={{
  display: "inline",
  verticalAlign: "middle",
  flexShrink: 0,
  background: "transparent"
}}>
    <rect ry="4" rx="4" height="40" width="40" y="0" x="0" fill="currentColor" fillOpacity="0.15" stroke="currentColor" strokeWidth="2" />
    <rect ry="4" rx="4" height="40" width="40" y="12" x="12" fill="currentColor" fillOpacity="0.15" stroke="currentColor" strokeWidth="2" />
    <path d="m18,22l12,0l0,4l-12,0l0,-4z" fill="currentColor" />
    <path d="m34,22l12,0l0,4l-12,0l0,-4z" fill="currentColor" />
    <path d="m18,36l4,0l0,-4l4,0l0,4l4,0l0,4l-4,0l0,4l-4,0l0,-4l-4,0l0,-4z" fill="currentColor" />
    <path d="m34,36l4,0l0,-4l4,0l0,4l4,0l0,4l-4,0l0,4l-4,0l0,-4l-4,0l0,-4z" fill="currentColor" />
  </svg>;

export const AzureIcon = () => <svg className="azure-icon" viewBox="0 0 18 18" width="12" height="12" style={{
  display: "inline",
  verticalAlign: "middle",
  flexShrink: 0,
  background: "transparent"
}}>
    <defs>
      <linearGradient id="azure-gradient" x1="9" y1="16.97" x2="9" y2="1.03" gradientUnits="userSpaceOnUse">
        <stop offset="0" stopColor="currentColor" />
        <stop offset="0.16" stopColor="currentColor" />
        <stop offset="0.53" stopColor="currentColor" />
        <stop offset="0.82" stopColor="currentColor" />
        <stop offset="1" stopColor="currentColor" />
      </linearGradient>
    </defs>
    <path d="M17,4v9.74l-4,3.28-6.2-2.26V17L3.29,12.41l10.23.8V4.44Zm-3.41.49L7.85,1V3.29L2.58,4.84,1,6.87v4.61l2.26,1V6.57Z" fill="url(#azure-gradient)" />
  </svg>;

Large pull requests can generate many findings, which can clutter the review and make it harder to focus on what matters. Qodo addresses this by showing only a subset by default, the rest collapse behind View all and stay one click away, nothing is discarded. You can also control how each finding's individual components (for example, description or code) are shown or expanded, separately for the summary comment and for inline comments.

This page describes how to control what's shown within a finding, not where it's published. For choosing whether findings appear inline, in the summary comment, both, or not at all by severity, see [Control review verbosity](/code-review/review-verbosity).

## Configure findings visibility in the Qodo portal (Recommended)

1. Log in to the Qodo portal.
2. Navigate to **Configurations** > **Display**.
3. Configure the following settings:

* **Finding overflow**: How many findings are shown before the rest collapse behind "View all." Set under **Overflow** > [Findings visible per group](/configuration/display#overflow).
* **Per-finding verbosity**: Whether each part of a finding is hidden, collapsed, or expanded in the summary comment. Set under **Findings** > [Finding content sections](/configuration/display#findings).
* **Show content section titles**: Shows a label above each finding part in the summary comment. Set under **Findings** > [Show content section titles](/configuration/display#findings).
* **Inline comment sections**: Whether each part of a finding is shown in the inline comment. Set under **Findings** > [Inline findings](/configuration/display#findings).
* **Link finding summary to inline findings**: Links a summary finding's title to its inline comment. Set under **Comment routing** > [Link finding summary to inline findings](/configuration/display#comments). Currently supported on Bitbucket and Gerrit only.
* **Resolved findings**: Whether resolved findings are shown, where they appear, and how much of the resolved section is shown. Set under [Resolved findings](/configuration/display#resolved-findings).

## Configure findings visibility in .pr\_agent.toml

### Finding overflow

<div style={{ display: "flex", alignItems: "center", gap: "6px", marginBottom: "1rem" }}>
  <Badge color="outline-provider" size="sm" shape="pill" icon="github">GitHub</Badge>
  <Badge color="outline-provider" size="sm" shape="pill" icon="gitlab">GitLab</Badge>
  <Badge color="outline-provider" size="sm" shape="pill"><AzureIcon />Azure DevOps</Badge>
</div>

Control how many findings are shown before the rest collapse behind **"View all"**.

```toml theme={null}
[review_agent_ux]
finding_overflow_count = 3
```

| Value | Behavior |
| - | - |
| `0` | All findings collapsed |
| `1`, `3` (default), `5` | Number of findings shown before "View all" |
| `-1` | All findings expanded (the portal shows this option as "All") |

### Resolved findings

Control whether resolved findings are shown, whether they stay in place or move to a separate section, and how much of that section is shown.

```toml theme={null}
[review_agent_ux]
show_resolved_findings = true
resolved_findings_placement = "resolved_section"
resolved_overflow_count = 0
```

`resolved_overflow_count` applies only when `resolved_findings_placement` is `"resolved_section"`. For more information about each value and how it renders by Git provider, see [Track resolved findings](/code-review/track-resolved-findings).

### Per-finding verbosity

<div style={{ display: "flex", alignItems: "center", gap: "6px", marginBottom: "1rem" }}>
  <Badge color="outline-provider" size="sm" shape="pill" icon="github">GitHub</Badge>
  <Badge color="outline-provider" size="sm" shape="pill" icon="gitlab">GitLab</Badge>
  <Badge color="outline-provider" size="sm" shape="pill"><AzureIcon />Azure DevOps</Badge>
</div>

For each part of a finding, control whether it's hidden, shown collapsed, or shown expanded in the summary comment. Each part is controlled by two keys: `render_*` sets whether the part is shown at all, `expand_*` sets whether it's expanded or collapsed when shown.

```toml theme={null}
[review_agent_ux]
render_description = true
expand_description = true
render_code = true
expand_code = false
render_recommendation = true
expand_recommendation = false
render_evidence = true
expand_evidence = false
expand_prompt = false
```

| Part | Keys | Default |
| - | - | - |
| Description | `render_description`, `expand_description` | Expanded |
| Code | `render_code`, `expand_code` | Collapsed |
| Relevance | `render_recommendation`, `expand_recommendation` | Collapsed |
| Evidence | `render_evidence`, `expand_evidence` | Collapsed |
| Agent prompt | `render_prompt`, `expand_prompt` | Collapsed |

To hide a part entirely, set its `render_*` key to `false`.

Agent prompt doesn't set `render_prompt` by default. Unset, it falls back to the legacy `show_prompt` key (`true`), which combined with `expand_prompt = false` gives it a default of Collapsed, not Hidden. Setting `render_prompt` explicitly overrides `show_prompt`.

### Show content section titles

<div style={{ display: "flex", alignItems: "center", gap: "6px", marginBottom: "1rem" }}>
  <Badge color="outline-provider" size="sm" shape="pill" icon="bitbucket">Bitbucket</Badge>
  <Badge color="outline-provider" size="sm" shape="pill"><GerritIcon />Gerrit</Badge>
</div>

Shows the section titles (Description, Code, Agent Prompt) above each finding part in the summary comment. Currently supported on Bitbucket and Gerrit only.

```toml theme={null}
[review_agent_ux]
show_subsection_names = false
```

Default: `false`.

### Inline comment sections

For each part of a finding, control whether it's shown in the inline comment attached to the code line, separately from the summary comment. Each part is either shown or hidden.

```toml theme={null}
[review_agent_ux]
inline_render_description = true
inline_render_code = false
inline_render_evidence = false
inline_render_recommendation = false
inline_render_prompt = true
```

| Part | Key | Default |
| - | - | - |
| Description | `inline_render_description` | Shown |
| Code | `inline_render_code` | Hidden |
| Relevance | `inline_render_recommendation` | Hidden |
| Evidence | `inline_render_evidence` | Hidden |
| Agent prompt | `inline_render_prompt` | Shown |

Unset, `inline_render_description` and `inline_render_prompt` follow the summary comment's `render_description` and `render_prompt`. `inline_render_code`, `inline_render_evidence`, and `inline_render_recommendation` stay hidden regardless of the summary comment's settings.

### Link finding summary to inline findings

<div style={{ display: "flex", alignItems: "center", gap: "6px", marginBottom: "1rem" }}>
  <Badge color="outline-provider" size="sm" shape="pill" icon="bitbucket">Bitbucket</Badge>
  <Badge color="outline-provider" size="sm" shape="pill"><GerritIcon />Gerrit</Badge>
</div>

When a finding is published as both a summary and an inline comment, link the summary finding's title to its inline comment.

```toml theme={null}
[review_agent_ux]
link_findings_to_inline_comments = true
```

Default: `true`. Currently supported on Bitbucket and Gerrit only. On GitHub, GitLab, and Azure DevOps, the summary comment is published before the inline comments exist, so there's no URL yet to link to, and the setting has no effect.

## Related resources

* [Anatomy of a Qodo Code Review](/code-review/comment-anatomy): The parts of the review comment and how to read them.
* [Track resolved findings in pull requests](/code-review/track-resolved-findings): Show resolved findings in place, in a separate section, or not at all.
* [Customize the code review experience](/configuration): What you can configure, and where to configure it.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.