> ## 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.

# Understand review comment size limits

> Learn how Qodo handles oversized review comments, what content gets trimmed first, and how to access the full findings in the Qodo portal.

When a review summary comment exceeds your Git provider's size limit, Qodo trims its content to fit. It removes less important content first, preserving findings for as long as possible. Warnings identify what was removed, and the full findings remain available in the Qodo portal.

## Why Qodo trims review comments

A Git provider does not accept a comment above its maximum size. Cutting the end off such a comment to make it fit can remove important content and break the comment's formatting. Instead, Qodo fits the comment within the limit by choosing what to leave out.

A comment within the limit is posted unchanged. Trimming applies only to the review summary comment, not to inline comments on code lines.

## Comment size limits by Git provider

The table lists the limit Qodo applies on each provider. On a number of providers, this limit is lower than the largest comment the provider accepts.

| Git provider | Limit Qodo applies |
| - | - |
| GitHub | 65,000 characters |
| GitLab | 65,000 characters |
| Bitbucket Cloud | 31,000 characters |
| Bitbucket Data Center | 32,000 characters |
| Azure DevOps | 149,500 characters |
| Gerrit | 16,000 bytes |

Qodo counts characters on every provider except Gerrit, where it counts bytes. As a result, on Gerrit, emoji and non-Latin characters use more of the limit than plain ASCII text.

## What Qodo trims first

When the review summary comment is over the limit, Qodo removes content in the order below, least important first, and skips any content the comment does not include. After each step, Qodo measures the comment again and stops as soon as it fits. As a result, a comment loses only as much content as it needs to.

| Order | Content Qodo removes | Warning shown |
| - | - | - |
| 1 | [Tip of the day](https://docs.qodo.ai/tips-and-tricks.md) | `non finding content trimmed` |
| 2 | [Previous reviews](https://docs.qodo.ai/code-review/comment-anatomy.md#previous-reviews-formerly-audit-trail) | `non finding content trimmed` |
| 3 | [Context sources](https://docs.qodo.ai/code-review/comment-anatomy.md#code-review-findings-overview) | `non finding content trimmed` |
| 4 | [Finding counters](https://docs.qodo.ai/code-review/comment-anatomy.md#code-review-findings-overview) | `non finding content trimmed` |
| 5 | [Code snippets](https://docs.qodo.ai/code-review/comment-anatomy.md#unpack-a-code-review-finding). Each finding keeps its file and line reference. | `inner finding content trimmed` |
| 6 | [Relevance](https://docs.qodo.ai/code-review/relevance.md) sections | `inner finding content trimmed` |
| 7 | [Evidence](https://docs.qodo.ai/code-review/comment-anatomy.md#unpack-a-code-review-finding) sections | `inner finding content trimmed` |
| 8 | [Agent prompts](https://docs.qodo.ai/code-review/comment-anatomy.md#unpack-a-code-review-finding) | `inner finding content trimmed` |
| 9 | [Resolved findings](https://docs.qodo.ai/code-review/track-resolved-findings.md) (✓ Resolved, ✗ Dismissed, and ⊖ Outdated) | `N lower severity findings trimmed` |
| 10 | [Open findings](https://docs.qodo.ai/code-review/comment-anatomy.md#code-review-findings-overview) | `N lower severity findings trimmed` |

In steps 5 to 10, Qodo starts from the last finding in the comment and works upward, removing content from lower-priority findings first. A finding is removed only after its code snippet, Relevance, Evidence, and Agent prompt sections have all been removed.
If a single finding is larger than the entire limit, Qodo shows that finding in part and adds this notice:

> [!NOTE]
>
> This finding exceeds the comment size limit and was truncated. View the full findings in the Qodo portal.

## Warnings for content removed from a comment

Qodo adds one warning for each kind of content it removed, just above the footer, with the most important first. A trimmed comment shows up to three warnings:

```text theme={null}
⚠️ Warning | Comment size exceeded, N lower severity findings trimmed View findings
⚠️ Warning | Comment size exceeded, inner finding content trimmed View findings
⚠️ Warning | Comment size exceeded, non finding content trimmed Learn more
```

| Warning | Description |
| - | - |
| `N lower severity findings trimmed` | Qodo removed N whole findings from the comment. With one finding, the warning reads `1 lower severity finding trimmed`. |
| `inner finding content trimmed` | Qodo removed code snippets, Relevance, Evidence, or Agent prompt sections from some findings. Those findings stay in the comment. |
| `non finding content trimmed` | Qodo removed the tip of the day, Previous reviews, Context sources, or finding counters. |

Each warning ends with a link:

* **View findings**: Opens the pull request's findings in the Qodo portal.
* **Learn more**: Opens this page. If the pull request's findings are not available in the Qodo portal, every warning shows this link instead of View findings.

GitHub, GitLab, and Azure DevOps show each warning in its own box. Bitbucket and Gerrit support standard Markdown only. As a result, each warning appears as a quoted line on those providers.

## Related resources

* [Anatomy of a Qodo Code Review](https://docs.qodo.ai/code-review/comment-anatomy.md): What each part of the review summary comment shows.
* [Monitor organization-wide pull request findings](https://docs.qodo.ai/governance/view-all-findings-in-organization.md): View every finding in the Qodo portal, including findings trimmed from a comment.
* [Configure Display settings in the Qodo portal](https://docs.qodo.ai/configuration/display.md#comment-parts): Choose which comment parts appear in the review summary comment.


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