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

# Optimize code review loops as you fix findings

> When you push fixes for Qodo's findings, Qodo focuses the next review on your recent changes, reducing noise, review latency, and cost while the pull request converges to a clean review faster.

When you push fixes for Qodo’s findings, Fix loop optimization focuses the next review on your recent code changes instead of reviewing the entire pull request again. This reduces noise, review latency, and cost as the pull request moves toward a clean review.

Fix loop optimization helps you:

* Reduce noise in follow-up reviews.
* Get follow-up reviews faster.
* Lower the cost of each follow-up review.

Fix loop optimization is enabled by default. The first review of a PR is never affected.

## Enable or disable fix loop optimization

### In the Qodo portal (Recommended)

1. Log in to the Qodo portal.
2. Navigate to **Configurations** > **Workflow** > **Code review**.
3. Turn **Fix loop optimization** on or off.

You can set this configuration for a workspace, a Git organization, or a single repository.

### In .pr\_agent.toml

Set enable\_fix\_loop\_optimization under the \[review\_agent] section:

```toml theme={null}
[review_agent]
enable_fix_loop_optimization = true
```

Set the value to true to enable fix loop optimization or false to disable it. The default is true.

## Related resources

* [Configure Qodo using the portal](https://docs.qodo.ai/configuration/portal-configuration.md): The recommended way to manage organization-wide and repository-level code review configuration.
* [Optimize AI effort with Review effort mode](https://docs.qodo.ai/code-review/use-qodo-in-prs/control-review-effort.md): Match review depth to the risk of each change.
* [Track resolved findings in pull requests](https://docs.qodo.ai/code-review/track-resolved-findings.md): See which findings Qodo marked as resolved across review rounds.


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